Help:Managing files

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>EvoEcu</sitename>
    <dbname>evoecu_mediawiki</dbname>
    <base>https://evoecu.logic.net/wiki/Main_Page</base>
    <generator>MediaWiki 1.39.11</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">EvoEcu</namespace>
      <namespace key="5" case="first-letter">EvoEcu talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Help:Managing files</title>
  <ns>12</ns>
  <id>20</id>
  <revision>
    <id>96</id>
    <timestamp>2008-06-30T18:36:55Z</timestamp>
    <contributor>
      <username>12.148.36.6</username>
      <id>0</id>
    </contributor>
    <comment>/* Listing files in the wiki */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2004" xml:space="preserve">{{PD Help Page}}
If file uploads are enabled, you can upload certain types of files to the wiki. This is particularly useful for uploading images, which you want to place on an article, but you can also upload other types of file.

==Upload a file==
# Prepare the file for upload. Make sure the file is exactly as you want it. Think about how big the file is.
# In the [[Help:Navigation#Sidebar|sidebar]], under '''toolbox''', click "Upload file"
# Next to the '''Source filename''', click '''Browse''' to locate the file on your computer.
# Change the '''Destination filename''' to something descriptive, if necessary.
# Fill in the '''Summary''', if necessary.
# Click the '''Upload file''' button.

If it is a large file, you may need to wait several seconds for the upload to complete.

== Using Images and Image Description Pages ==

After you've uploaded a file, you can use it in an article, with some special wiki syntax to create the link. See [[Help:Images]].

Your file gets its very own 'Image Description Page' within the wiki (even if it isn't an image). You should edit this page to provide more information about the file. For example, many wiki projects are quite sensitive to copyright issues, and so you should explain where you got the file from, and what its copyright status is, on the description page. Any other useful descriptive notes could also be added there.

== Listing files in the wiki ==

There are a number of Special Pages to help you view and manage files which have been uploaded. Go to 'Special Pages' (in the toolbox on the left) and then see...

* [[Special:Newimages|Gallery of new images]] - If you just uploaded one, you will see it here.  
* [[Special:Imagelist|File list]] shows all of the files
* [[Special:Unusedimages|Unused images]] helps you track down files which might not be needed.

See [[Help:Special pages]] for details of the other information available here.

{{Languages|Help:Managing files}}
[[Category:Help|Managing files]]
[[Category:Upload]]</text>
    <sha1>3f5e818f4c6c5cf9a26d7d5f1c2ca87258f66c92</sha1>
  </revision>
  <revision>
    <id>97</id>
    <parentid>96</parentid>
    <timestamp>2008-07-29T18:30:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2004" xml:space="preserve">{{PD Help Page}}
If file uploads are enabled, you can upload certain types of files to the wiki. This is particularly useful for uploading images, which you want to place on an article, but you can also upload other types of file.

==Upload a file==
# Prepare the file for upload. Make sure the file is exactly as you want it. Think about how big the file is.
# In the [[Help:Navigation#Sidebar|sidebar]], under '''toolbox''', click "Upload file"
# Next to the '''Source filename''', click '''Browse''' to locate the file on your computer.
# Change the '''Destination filename''' to something descriptive, if necessary.
# Fill in the '''Summary''', if necessary.
# Click the '''Upload file''' button.

If it is a large file, you may need to wait several seconds for the upload to complete.

== Using Images and Image Description Pages ==

After you've uploaded a file, you can use it in an article, with some special wiki syntax to create the link. See [[Help:Images]].

Your file gets its very own 'Image Description Page' within the wiki (even if it isn't an image). You should edit this page to provide more information about the file. For example, many wiki projects are quite sensitive to copyright issues, and so you should explain where you got the file from, and what its copyright status is, on the description page. Any other useful descriptive notes could also be added there.

== Listing files in the wiki ==

There are a number of Special Pages to help you view and manage files which have been uploaded. Go to 'Special Pages' (in the toolbox on the left) and then see...

* [[Special:Newimages|Gallery of new images]] - If you just uploaded one, you will see it here.  
* [[Special:Imagelist|File list]] shows all of the files
* [[Special:Unusedimages|Unused images]] helps you track down files which might not be needed.

See [[Help:Special pages]] for details of the other information available here.

{{Languages|Help:Managing files}}
[[Category:Help|Managing files]]
[[Category:Upload]]</text>
    <sha1>3f5e818f4c6c5cf9a26d7d5f1c2ca87258f66c92</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Sysop deleting and undeleting</title>
  <ns>12</ns>
  <id>35</id>
  <revision>
    <id>126</id>
    <timestamp>2008-07-07T21:54:01Z</timestamp>
    <contributor>
      <username>128.240.229.67</username>
      <id>0</id>
    </contributor>
    <comment>a minor typo in "situations"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2196" xml:space="preserve">{{PD Help Page}}
'''Deleting a page''' is a straightforward operation for anyone with [[Help:Sysops and permissions|sysop permissions]]. Users without such permissions can still remove text from wiki pages, or propose/request that a page should be deleted. See [[Help:Deleting a page]].

== Before deleting ==
Sysops should also be aware of the general advice given on [[Help:Deleting a page]] (In particular, note that there are many situations where a deleting is too drastic. Often a redirect is more appropriate for example)

Before deleting you could perform various checks:
* Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the wiki community to do it.
* Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalise a page, which then led to a deletion proposal? 

The care taken over these things might depend on the size of the wiki community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever. 

== Use the 'delete' tab ==
Sysops should see a 'delete' tab at the top of every page. Click this to delete the page. You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

== Undeleting ==
To undelete a page you must navigate to the exact page name of the page. You can find this in the deletion log ([[Special:Log]]) if you dont remember it.

You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.</text>
    <sha1>99f2ca04836f6f7af71c6febc804cf27d441926e</sha1>
  </revision>
  <revision>
    <id>127</id>
    <parentid>126</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2196" xml:space="preserve">{{PD Help Page}}
'''Deleting a page''' is a straightforward operation for anyone with [[Help:Sysops and permissions|sysop permissions]]. Users without such permissions can still remove text from wiki pages, or propose/request that a page should be deleted. See [[Help:Deleting a page]].

== Before deleting ==
Sysops should also be aware of the general advice given on [[Help:Deleting a page]] (In particular, note that there are many situations where a deleting is too drastic. Often a redirect is more appropriate for example)

Before deleting you could perform various checks:
* Use the "What links here" tool. This gives an indication as to how important a page is, and what subjects it relates to. Perhaps the page is still linked to prominently from many places. All incoming links will become red links if you proceed with the delete. Ideally all incoming links should be changed/removed, if there is genuinely no need for this page to exist. You could do this work prior to deleting, or ask others in the wiki community to do it.
* Check the page history and the associated talk page. Who was proposing the deletion? Does anyone disagree? Has it been properly discussed? Did people have adequate time to raise objections? Did somebody vandalise a page, which then led to a deletion proposal? 

The care taken over these things might depend on the size of the wiki community, and how clear-cut the case for deletion is. Remember that only sysop users can undo a delete action, so to a normal user the information appears to be lost forever. 

== Use the 'delete' tab ==
Sysops should see a 'delete' tab at the top of every page. Click this to delete the page. You will be asked to confirm, and to supply a "Reason for deletion". This is a short textual description of why the page is being deleted. Your action will appear on the recent changes display, and in the deletion log ([[Special:Log]]).

== Undeleting ==
To undelete a page you must navigate to the exact page name of the page. You can find this in the deletion log ([[Special:Log]]) if you dont remember it.

You should then see a link to "View or restore n deleted edits". Tick the box next to the revision you wish to restore.</text>
    <sha1>99f2ca04836f6f7af71c6febc804cf27d441926e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Range blocks</title>
  <ns>12</ns>
  <id>29</id>
  <revision>
    <id>114</id>
    <timestamp>2008-07-15T15:26:06Z</timestamp>
    <contributor>
      <username>80.229.172.200</username>
      <id>0</id>
    </contributor>
    <comment>wikipedia IW link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7967" xml:space="preserve">{{PD Help Page}}
'''Range blocks''' are technical restrictions applied through [[Special:Blockip]] to a group of [http://en.wikipedia.org/wiki/IP_addresses IP addresses] that prevent them from editing, creating new accounts, sending email through the wiki interface, et cetera. Registered accounts editing from these IP addresses will also be blocked, unless you check the box to only block anonymous editors.

Range blocking is enabled on all [http://en.wikipedia.org/wiki/Wikimedia_Foundation Wikimedia] wikis; to enable it on other wikis, add "&lt;code&gt;{{mediawiki|Manual:$wgSysopRangeBans|$wgSysopRangeBans}} = true;&lt;/code&gt;" in &lt;tt&gt;{{mediawiki|Manual:LocalSettings.php|LocalSettings.php}}&lt;/tt&gt;.

To block an IP range from [[Special:Blockip]], enter the first IP address in the range followed by a forward slash and a [http://en.wikipedia.org/wiki/Classless_inter-domain_routing Classless inter-domain routing] (CIDR) suffix. '''You should avoid performing range blocks unless you understand what you are doing, or you may end up blocking tens of thousands of people who are not the problem!'''

==Technical explanation==
CIDR notation is written as the IP address, a slash, and the CIDR affix (for example, the IPv4 "&lt;code&gt;10.2.3.41/24&lt;/code&gt;" or IPv6 "&lt;code&gt;a3:b:c1:d:e:f:1:21/24&lt;/code&gt;"). The CIDR affix is the number of starting digits every IP address in the range have in common when written in binary. 

For example: "&lt;code&gt;10.10.1.32&lt;/code&gt;" is binary "&lt;code&gt;00001010.00001010.00000001.00100000&lt;/code&gt;", so &lt;code&gt;10.10.1.32/27&lt;/code&gt; will match the first 27 digits ("&lt;code&gt;&lt;u&gt;00001010&lt;/u&gt;.&lt;u&gt;00001010&lt;/u&gt;.&lt;u&gt;00000001&lt;/u&gt;.&lt;u&gt;001&lt;/u&gt;00000&lt;/code&gt;"). The IP addresses &lt;code&gt;10.10.1.32&lt;/code&gt;–&lt;code&gt;10.10.1.63&lt;/code&gt;, when converted to binary, all have the same 27 first digits and will be blocked if &lt;code&gt;10.10.1.32/27&lt;/code&gt; is blocked.

As the CIDR affix increases, the block affects fewer IP addresses (see [[#Table|table of example ranges]]). CIDR affixes are not the same for IPv4 addresses as they are for IPv6 addresses.

==Calculating the CIDR affix==
You can use the [[#Table|table of sample ranges]] below to guess the range, use a computer script, or manually calculate the range.

===Conversion to binary===
The first step in manually calculating a range is to convert the first and last IP address to binary representation. (This assumes you're not using a computer script, which can probably calculate the range for you anyway.) An IP address is composed of four groups of eight ones and zeros. Each group represents a number from 0 to 255. To convert a number to binary, you can use a [http://www.ccci.com/tools/subcalc/binary.html reference table] or know the value of each binary digit:
{| class="prettytable" style="text-align:center;"
|-
| 1
| 1
| 1
| 1
| 1
| 1
| 1
| 1
|-
| 128
| 64
| 32
| 16
| 8
| 4
| 2
| 1
|}

Proceeding from left to right, fill in '1' if the number is at least that value, and subtract that value (if it's not, fill in '0' and don't subtract). For example, to calculate 240:
# 240 is at least 128, so place 1 and subtract 128.
# 112 (240-128) is at least 64, so place 1 and subtract 64.
# 48 (112-64) is at least 32, so place 1 and subtract 48.
# 16 (48-32) is at least 16, so place 1 and subtract 16.
# Since the remaining value is zero, all the remaining places are '0'.
Thus, 240 is 1111 0000 because it can be represented as 128+64+32+16+0+0+0+0.

===Calculate range===
# Place both IP addresses one atop the other, and count how many starting digits are exactly alike. This is the CIDR affix.
# Double-check! Being off by one digit could extend your block by thousands of addresses.

The example below calculates the CIDR range between 69.208.0.0 and 69.208.0.255. Note that this is a simple example; some groups of IP addresses do not so neatly fit CIDR affixes, and need multiple different-sized blocks to block the exact range.
 IP addresses:
   69.208.0.0
   69.208.0.255
 &amp;nbsp;
 Convert to binary:
   0100 0101.1101 0000.0000 0000.0000 0000
   0100 0101.1101 0000.0000 0000.1111 1111
 &amp;nbsp;
 Count identical first numbers:
   '''0100 0101.1101 0000.0000 0000'''.0000 0000
   '''0100 0101.1101 0000.0000 0000'''.1111 1111
   |____________________________|
             24 digits
  &amp;nbsp;
 CIDR range:
   69.208.0.0/24
&lt;/pre&gt;

===&lt;span id="Table"&gt;Table of sample ranges&lt;/span&gt;===
The table below shows the IP blocks each CIDR suffix affects. Note that MediaWiki only supports blocking CIDR suffixes 16&amp;ndash;32.

{| class="prettytable"
! CIDR
! Start Range
! End Range
! Total addresses
! Bits selected in IP address
|- style="color:gray;"
| 69.208.0.0'''/0'''
| 0.0.0.0
| 255.255.255.255
| 4,294,967,296
| ********.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/1'''
| 0.0.0.0
| 127.255.255.255
| 2,147,483,648
| 0*******.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/4'''
| 65.0.0.0
| 79.255.255.255
| 268,435,456
| 0100****.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/8'''
| 69.0.0.0
| 69.255.255.255
| 67,108,864
| 01000101.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/11'''
| 69.208.0.0
| 69.238.255.255
| 2,197,152
| 01000101.110*****.********.********
|- style="color:gray;"
| 69.208.0.0'''/12'''
| 69.208.0.0
| 69.223.255.255
| 1,048,576
| 01000101.1101****.********.********
|- style="color:gray;"
| 69.208.0.0'''/13'''
| 69.208.0.0
| 69.215.255.255
| 524,288
| 01000101.11010***.********.********
|- style="color:gray;"
| 69.208.0.0'''/14'''
| 69.208.0.0
| 69.211.255.255
| 262,144
| 01000101.110100**.********.********
|- style="color:gray;"
| 69.208.0.0'''/15'''
| 69.208.0.0
| 69.209.255.255
| 131,072
| 01000101.1101000*.********.********
|-
| 69.208.0.0'''/16'''
| 69.208.0.0
| 69.208.255.255
| 65,536
| 01000101.11010000.********.********
|-
| 69.208.0.0'''/17'''
| 69.208.0.0
| 69.208.127.255
| 32,768
| 01000101.11010000.0*******.********
|-
| 69.208.0.0'''/18'''
| 69.208.0.0
| 69.208.63.255
| 16,384
| 01000101.11010000.00******.********
|-
| 69.208.0.0'''/19'''
| 69.208.0.0
| 69.208.31.255
| 8,192
| 01000101.11010000.000*****.********
|-
| 69.208.0.0'''/20'''
| 69.208.0.0
| 69.208.15.255
| 4,096
| 01000101.11010000.0000****.********
|-
| 69.208.0.0'''/21'''
| 69.208.0.0
| 69.208.7.255
| 2,048
| 01000101.11010000.00000***.********
|-
| 69.208.0.0'''/22'''
| 69.208.0.0
| 69.208.3.255
| 1,024
| 01000101.11010000.000000**.********
|-
| 69.208.0.0'''/23'''
| 69.208.0.0
| 69.208.1.255
| 512
| 01000101.11010000.0000000*.********
|-
| 69.208.0.0'''/24'''
| 69.208.0.0
| 69.208.0.255
| 256
| 01000101.11010000.00000000.********
|-
| 69.208.0.0'''/25'''
| 69.208.0.0
| 69.208.0.127
| 128
| 01000101.11010000.00000000.0*******
|-
| 69.208.0.0'''/26'''
| 69.208.0.0
| 69.208.0.63
| 64
| 01000101.11010000.00000000.00******
|-
| 69.208.0.0'''/27'''
| 69.208.0.0
| 69.208.0.31
| 32
| 01000101.11010000.00000000.000*****
|-
| 69.208.0.0'''/28'''
| 69.208.0.0
| 69.208.0.15
| 16
| 01000101.11010000.00000000.0000****
|-
| 69.208.0.0'''/29'''
| 69.208.0.0
| 69.208.0.7
| 8
| 01000101.11010000.00000000.00000***
|-
| 69.208.0.0'''/30'''
| 69.208.0.0
| 69.208.0.3
| 4
| 01000101.11010000.00000000.000000**
|-
| 69.208.0.0'''/31'''
| 69.208.0.0
| 69.208.0.1
| 2
| 01000101.11010000.00000000.0000000*
|-
| 69.208.0.0'''/32'''
| 69.208.0.0
| 69.208.0.0
| 1
| 01000101.11010000.00000000.00000000
|}

==References==
* [[wikipedia:Classless Inter-Domain Routing|Classless Inter-Domain Routing]]
* [http://www.ccci.com/tools/subcalc/binary.html Converting IP addresses to binary]

==External links==
* [http://www.find-ip-address.org/ip-country/ IP Address Ranges Block] gives you complete IP ranges for certain country.
* [http://apps.csc.fi/laskin2.html Netmask calculator] which helps in making the correct decision for range blocks.
* [http://tools.wikimedia.de/~chm/blockcalc.php Rangeblock-Calculator] gives you the range you should use when blocking.

{{Languages|Help:Range blocks}}

[[Category:Help|Range blocks]]</text>
    <sha1>03d564c325d89a8fd5e55dea75380ab05a26f94e</sha1>
  </revision>
  <revision>
    <id>115</id>
    <parentid>114</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7967" xml:space="preserve">{{PD Help Page}}
'''Range blocks''' are technical restrictions applied through [[Special:Blockip]] to a group of [http://en.wikipedia.org/wiki/IP_addresses IP addresses] that prevent them from editing, creating new accounts, sending email through the wiki interface, et cetera. Registered accounts editing from these IP addresses will also be blocked, unless you check the box to only block anonymous editors.

Range blocking is enabled on all [http://en.wikipedia.org/wiki/Wikimedia_Foundation Wikimedia] wikis; to enable it on other wikis, add "&lt;code&gt;{{mediawiki|Manual:$wgSysopRangeBans|$wgSysopRangeBans}} = true;&lt;/code&gt;" in &lt;tt&gt;{{mediawiki|Manual:LocalSettings.php|LocalSettings.php}}&lt;/tt&gt;.

To block an IP range from [[Special:Blockip]], enter the first IP address in the range followed by a forward slash and a [http://en.wikipedia.org/wiki/Classless_inter-domain_routing Classless inter-domain routing] (CIDR) suffix. '''You should avoid performing range blocks unless you understand what you are doing, or you may end up blocking tens of thousands of people who are not the problem!'''

==Technical explanation==
CIDR notation is written as the IP address, a slash, and the CIDR affix (for example, the IPv4 "&lt;code&gt;10.2.3.41/24&lt;/code&gt;" or IPv6 "&lt;code&gt;a3:b:c1:d:e:f:1:21/24&lt;/code&gt;"). The CIDR affix is the number of starting digits every IP address in the range have in common when written in binary. 

For example: "&lt;code&gt;10.10.1.32&lt;/code&gt;" is binary "&lt;code&gt;00001010.00001010.00000001.00100000&lt;/code&gt;", so &lt;code&gt;10.10.1.32/27&lt;/code&gt; will match the first 27 digits ("&lt;code&gt;&lt;u&gt;00001010&lt;/u&gt;.&lt;u&gt;00001010&lt;/u&gt;.&lt;u&gt;00000001&lt;/u&gt;.&lt;u&gt;001&lt;/u&gt;00000&lt;/code&gt;"). The IP addresses &lt;code&gt;10.10.1.32&lt;/code&gt;–&lt;code&gt;10.10.1.63&lt;/code&gt;, when converted to binary, all have the same 27 first digits and will be blocked if &lt;code&gt;10.10.1.32/27&lt;/code&gt; is blocked.

As the CIDR affix increases, the block affects fewer IP addresses (see [[#Table|table of example ranges]]). CIDR affixes are not the same for IPv4 addresses as they are for IPv6 addresses.

==Calculating the CIDR affix==
You can use the [[#Table|table of sample ranges]] below to guess the range, use a computer script, or manually calculate the range.

===Conversion to binary===
The first step in manually calculating a range is to convert the first and last IP address to binary representation. (This assumes you're not using a computer script, which can probably calculate the range for you anyway.) An IP address is composed of four groups of eight ones and zeros. Each group represents a number from 0 to 255. To convert a number to binary, you can use a [http://www.ccci.com/tools/subcalc/binary.html reference table] or know the value of each binary digit:
{| class="prettytable" style="text-align:center;"
|-
| 1
| 1
| 1
| 1
| 1
| 1
| 1
| 1
|-
| 128
| 64
| 32
| 16
| 8
| 4
| 2
| 1
|}

Proceeding from left to right, fill in '1' if the number is at least that value, and subtract that value (if it's not, fill in '0' and don't subtract). For example, to calculate 240:
# 240 is at least 128, so place 1 and subtract 128.
# 112 (240-128) is at least 64, so place 1 and subtract 64.
# 48 (112-64) is at least 32, so place 1 and subtract 48.
# 16 (48-32) is at least 16, so place 1 and subtract 16.
# Since the remaining value is zero, all the remaining places are '0'.
Thus, 240 is 1111 0000 because it can be represented as 128+64+32+16+0+0+0+0.

===Calculate range===
# Place both IP addresses one atop the other, and count how many starting digits are exactly alike. This is the CIDR affix.
# Double-check! Being off by one digit could extend your block by thousands of addresses.

The example below calculates the CIDR range between 69.208.0.0 and 69.208.0.255. Note that this is a simple example; some groups of IP addresses do not so neatly fit CIDR affixes, and need multiple different-sized blocks to block the exact range.
 IP addresses:
   69.208.0.0
   69.208.0.255
 &amp;nbsp;
 Convert to binary:
   0100 0101.1101 0000.0000 0000.0000 0000
   0100 0101.1101 0000.0000 0000.1111 1111
 &amp;nbsp;
 Count identical first numbers:
   '''0100 0101.1101 0000.0000 0000'''.0000 0000
   '''0100 0101.1101 0000.0000 0000'''.1111 1111
   |____________________________|
             24 digits
  &amp;nbsp;
 CIDR range:
   69.208.0.0/24
&lt;/pre&gt;

===&lt;span id="Table"&gt;Table of sample ranges&lt;/span&gt;===
The table below shows the IP blocks each CIDR suffix affects. Note that MediaWiki only supports blocking CIDR suffixes 16&amp;ndash;32.

{| class="prettytable"
! CIDR
! Start Range
! End Range
! Total addresses
! Bits selected in IP address
|- style="color:gray;"
| 69.208.0.0'''/0'''
| 0.0.0.0
| 255.255.255.255
| 4,294,967,296
| ********.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/1'''
| 0.0.0.0
| 127.255.255.255
| 2,147,483,648
| 0*******.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/4'''
| 65.0.0.0
| 79.255.255.255
| 268,435,456
| 0100****.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/8'''
| 69.0.0.0
| 69.255.255.255
| 67,108,864
| 01000101.********.********.********
|- style="color:gray;"
| 69.208.0.0'''/11'''
| 69.208.0.0
| 69.238.255.255
| 2,197,152
| 01000101.110*****.********.********
|- style="color:gray;"
| 69.208.0.0'''/12'''
| 69.208.0.0
| 69.223.255.255
| 1,048,576
| 01000101.1101****.********.********
|- style="color:gray;"
| 69.208.0.0'''/13'''
| 69.208.0.0
| 69.215.255.255
| 524,288
| 01000101.11010***.********.********
|- style="color:gray;"
| 69.208.0.0'''/14'''
| 69.208.0.0
| 69.211.255.255
| 262,144
| 01000101.110100**.********.********
|- style="color:gray;"
| 69.208.0.0'''/15'''
| 69.208.0.0
| 69.209.255.255
| 131,072
| 01000101.1101000*.********.********
|-
| 69.208.0.0'''/16'''
| 69.208.0.0
| 69.208.255.255
| 65,536
| 01000101.11010000.********.********
|-
| 69.208.0.0'''/17'''
| 69.208.0.0
| 69.208.127.255
| 32,768
| 01000101.11010000.0*******.********
|-
| 69.208.0.0'''/18'''
| 69.208.0.0
| 69.208.63.255
| 16,384
| 01000101.11010000.00******.********
|-
| 69.208.0.0'''/19'''
| 69.208.0.0
| 69.208.31.255
| 8,192
| 01000101.11010000.000*****.********
|-
| 69.208.0.0'''/20'''
| 69.208.0.0
| 69.208.15.255
| 4,096
| 01000101.11010000.0000****.********
|-
| 69.208.0.0'''/21'''
| 69.208.0.0
| 69.208.7.255
| 2,048
| 01000101.11010000.00000***.********
|-
| 69.208.0.0'''/22'''
| 69.208.0.0
| 69.208.3.255
| 1,024
| 01000101.11010000.000000**.********
|-
| 69.208.0.0'''/23'''
| 69.208.0.0
| 69.208.1.255
| 512
| 01000101.11010000.0000000*.********
|-
| 69.208.0.0'''/24'''
| 69.208.0.0
| 69.208.0.255
| 256
| 01000101.11010000.00000000.********
|-
| 69.208.0.0'''/25'''
| 69.208.0.0
| 69.208.0.127
| 128
| 01000101.11010000.00000000.0*******
|-
| 69.208.0.0'''/26'''
| 69.208.0.0
| 69.208.0.63
| 64
| 01000101.11010000.00000000.00******
|-
| 69.208.0.0'''/27'''
| 69.208.0.0
| 69.208.0.31
| 32
| 01000101.11010000.00000000.000*****
|-
| 69.208.0.0'''/28'''
| 69.208.0.0
| 69.208.0.15
| 16
| 01000101.11010000.00000000.0000****
|-
| 69.208.0.0'''/29'''
| 69.208.0.0
| 69.208.0.7
| 8
| 01000101.11010000.00000000.00000***
|-
| 69.208.0.0'''/30'''
| 69.208.0.0
| 69.208.0.3
| 4
| 01000101.11010000.00000000.000000**
|-
| 69.208.0.0'''/31'''
| 69.208.0.0
| 69.208.0.1
| 2
| 01000101.11010000.00000000.0000000*
|-
| 69.208.0.0'''/32'''
| 69.208.0.0
| 69.208.0.0
| 1
| 01000101.11010000.00000000.00000000
|}

==References==
* [[wikipedia:Classless Inter-Domain Routing|Classless Inter-Domain Routing]]
* [http://www.ccci.com/tools/subcalc/binary.html Converting IP addresses to binary]

==External links==
* [http://www.find-ip-address.org/ip-country/ IP Address Ranges Block] gives you complete IP ranges for certain country.
* [http://apps.csc.fi/laskin2.html Netmask calculator] which helps in making the correct decision for range blocks.
* [http://tools.wikimedia.de/~chm/blockcalc.php Rangeblock-Calculator] gives you the range you should use when blocking.

{{Languages|Help:Range blocks}}

[[Category:Help|Range blocks]]</text>
    <sha1>03d564c325d89a8fd5e55dea75380ab05a26f94e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:M-en-pagetabs.png</title>
  <ns>6</ns>
  <id>57</id>
  <revision>
    <id>175</id>
    <timestamp>2008-07-24T01:23:58Z</timestamp>
    <contributor>
      <username>86.141.61.48</username>
      <id>0</id>
    </contributor>
    <comment>removed multiple spaces</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">== Summary ==
Example page tabs screenshot for use in public domain help pages.

I grabbed this image and release it to the public domain, assuming that Mediawiki does not impose any restrictions on screenshots.

== Licensing ==
{{PD}}</text>
    <sha1>2bdda403a1ae9171486d3f70a67704e34fbd287d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Talk pages</title>
  <ns>12</ns>
  <id>13</id>
  <revision>
    <id>82</id>
    <timestamp>2008-07-27T10:42:04Z</timestamp>
    <contributor>
      <username>71.173.186.151</username>
      <id>0</id>
    </contributor>
    <comment>/* Editing discussions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6564" xml:space="preserve">{{PD Help Page}}

Every wiki page has an associated talk page which can be used for discussion and communicating with other users. Talk pages can be accessed by clicking the ''Discussion'' tab at the top of the page. Simply edit the page as normal to add your comment.

A talk page is actually very similar to any other wiki page, but it is in the 'talk' namespace, to keep it separate from the articles in the 'main' namespace (See [[Help:namespaces]]) As with any wiki page, you can edit it, link to it, and view the editing history.

== Editing conventions on talk pages ==
Having discussions on a free-form wiki page will seem strange at first. It helps if everyone follows some simple editing conventions:

* Always sign your name after your comments. Use the four tildes '&lt;tt&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/tt&gt;' wiki syntax (or the toolbar button)
* Start a new discussion with a &lt;tt&gt;&lt;nowiki&gt;==level 2 heading==&lt;/nowiki&gt;&lt;/tt&gt; at the bottom of the page (or use the '+' tab)
* Indent replies with colons (':') at the beginning of the line.

== Example ==
Here is an example discussion, following the talk page conventions:

{| align="center" {{Prettytable}}
|-
|{{Hl2}} |'''Wiki text'''	
|{{Hl2}} |'''Formatted talk page'''
|-
|


&lt;tt&gt;&lt;nowiki&gt;== More spiders information needed ==&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;
|
== More spiders information needed ==
This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)
: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)
:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)
::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)
|}


== Editing discussions ==
Having discussions on a free-form wiki page will seem strange at first. It has some advantages over the conventional rigid forum format, but it can get a little messy. As with other wiki pages, anyone can help with tidying up discussions, to conform to the editing conventions e.g. add signatures and headings where they are missing.

Clearly we also have the opportunity to edit other people's comments. It is generally bad etiquette to modify somebody else's wording (Better to just add your own comment with your corrections) But it can be acceptable to...

;Modify discussion headings
:Change wording or append words to the discussion headings, to better describe the topic of discussion. Note that good descriptive headings become important when many discussions start to fill the page.
;Move discussions to a different page
:If discussions are put in the wrong place on the wiki, and are better associated with different talk page, then you could just move the discussion by cut &amp; paste. This is potentially confusing, for the people posting, but can be important for keeping things tidy. You could leave the discussion in the wrong place for a few days/weeks grace before tidying it. You could leave a link behind explaining that a discussion was moved, or if not, you should link within the edit summary.
;Delete discussions when they are out-of-date
:Discussions can often get left lying around on a talk page long after the issue is no longer relevant. It's usually a good idea to reply to saying "I think this is now resolved", but sooner or later it's time to just blow away the old discussions (they are of course preserved in the editing history)
;Split a post into several discussions
:It may be appropriate to do this, if somebody has raised several points which need to be answered separately. However you should always be respectful to other people's words. Does their post still make sense if you split it up?

== Building articles - Discussing articles ==
It is usually best to keep focused on the task of building a wiki article, and use discussion pages only to support this process. The topic of conversation should generally revolve around what needs to be done to make the associated article better. Remember that editing the article itself is often a more effective means of communicating. It can be more difficult, requiring you to balance your views alongside those of others, but it can also be more rewarding. This is how the community of wiki editors will make progress. Often it will feel more natural to engage in heated debate on a talk page (or indeed any other contact channel) but in fact the wiki article itself can offer a powerful means of reaching middle-ground. Think about how to portray both sides of the argument (e.g. listing advantages and disadvantages) and you may find the debate evaporates.

== User Talk pages ==
A "user talk page" is a talk page associated with somebody's "user page" (See [[Help:User page]])  This is a place to leave messages for a particular wiki user.

This can function as a kind of messaging system. Users receive a prominent notification when new messages have been left on their talk page. They may be notified by email as well, although this cannot always be relied upon (since the email notification feature must be activated by supplying a valid email address, and clicking a confirmation link). If you don't get a response to your user talk page message, try looking for other contact details which they may have supplied on their user page.

Note that the messages are not private, and others can join in the conversation.

{{Languages|Help:Talk pages}}

[[Category:Help|Talk pages]]</text>
    <sha1>a4bedd7a9e2b7c24910b552dc2d1fbdcd0732dbd</sha1>
  </revision>
  <revision>
    <id>83</id>
    <parentid>82</parentid>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6564" xml:space="preserve">{{PD Help Page}}

Every wiki page has an associated talk page which can be used for discussion and communicating with other users. Talk pages can be accessed by clicking the ''Discussion'' tab at the top of the page. Simply edit the page as normal to add your comment.

A talk page is actually very similar to any other wiki page, but it is in the 'talk' namespace, to keep it separate from the articles in the 'main' namespace (See [[Help:namespaces]]) As with any wiki page, you can edit it, link to it, and view the editing history.

== Editing conventions on talk pages ==
Having discussions on a free-form wiki page will seem strange at first. It helps if everyone follows some simple editing conventions:

* Always sign your name after your comments. Use the four tildes '&lt;tt&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/tt&gt;' wiki syntax (or the toolbar button)
* Start a new discussion with a &lt;tt&gt;&lt;nowiki&gt;==level 2 heading==&lt;/nowiki&gt;&lt;/tt&gt; at the bottom of the page (or use the '+' tab)
* Indent replies with colons (':') at the beginning of the line.

== Example ==
Here is an example discussion, following the talk page conventions:

{| align="center" {{Prettytable}}
|-
|{{Hl2}} |'''Wiki text'''	
|{{Hl2}} |'''Formatted talk page'''
|-
|


&lt;tt&gt;&lt;nowiki&gt;== More spiders information needed ==&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;tt&gt;&lt;nowiki&gt;::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)&lt;/nowiki&gt;&lt;/tt&gt;
|
== More spiders information needed ==
This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)
: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)
:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)
::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)
|}


== Editing discussions ==
Having discussions on a free-form wiki page will seem strange at first. It has some advantages over the conventional rigid forum format, but it can get a little messy. As with other wiki pages, anyone can help with tidying up discussions, to conform to the editing conventions e.g. add signatures and headings where they are missing.

Clearly we also have the opportunity to edit other people's comments. It is generally bad etiquette to modify somebody else's wording (Better to just add your own comment with your corrections) But it can be acceptable to...

;Modify discussion headings
:Change wording or append words to the discussion headings, to better describe the topic of discussion. Note that good descriptive headings become important when many discussions start to fill the page.
;Move discussions to a different page
:If discussions are put in the wrong place on the wiki, and are better associated with different talk page, then you could just move the discussion by cut &amp; paste. This is potentially confusing, for the people posting, but can be important for keeping things tidy. You could leave the discussion in the wrong place for a few days/weeks grace before tidying it. You could leave a link behind explaining that a discussion was moved, or if not, you should link within the edit summary.
;Delete discussions when they are out-of-date
:Discussions can often get left lying around on a talk page long after the issue is no longer relevant. It's usually a good idea to reply to saying "I think this is now resolved", but sooner or later it's time to just blow away the old discussions (they are of course preserved in the editing history)
;Split a post into several discussions
:It may be appropriate to do this, if somebody has raised several points which need to be answered separately. However you should always be respectful to other people's words. Does their post still make sense if you split it up?

== Building articles - Discussing articles ==
It is usually best to keep focused on the task of building a wiki article, and use discussion pages only to support this process. The topic of conversation should generally revolve around what needs to be done to make the associated article better. Remember that editing the article itself is often a more effective means of communicating. It can be more difficult, requiring you to balance your views alongside those of others, but it can also be more rewarding. This is how the community of wiki editors will make progress. Often it will feel more natural to engage in heated debate on a talk page (or indeed any other contact channel) but in fact the wiki article itself can offer a powerful means of reaching middle-ground. Think about how to portray both sides of the argument (e.g. listing advantages and disadvantages) and you may find the debate evaporates.

== User Talk pages ==
A "user talk page" is a talk page associated with somebody's "user page" (See [[Help:User page]])  This is a place to leave messages for a particular wiki user.

This can function as a kind of messaging system. Users receive a prominent notification when new messages have been left on their talk page. They may be notified by email as well, although this cannot always be relied upon (since the email notification feature must be activated by supplying a valid email address, and clicking a confirmation link). If you don't get a response to your user talk page message, try looking for other contact details which they may have supplied on their user page.

Note that the messages are not private, and others can join in the conversation.

{{Languages|Help:Talk pages}}

[[Category:Help|Talk pages]]</text>
    <sha1>a4bedd7a9e2b7c24910b552dc2d1fbdcd0732dbd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>30</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T16:38:17Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="449" xml:space="preserve">&lt;big&gt;'''MediaWiki has been successfully installed.'''&lt;/big&gt;

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==

* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</text>
    <sha1>08fc850f2898611c250d639e30f69532b5a016f8</sha1>
  </revision>
  <revision>
    <id>29</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T17:52:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8579" xml:space="preserve">The [[Mitsubishi Lancer Evolution]] has a powerful stock [[Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [http://openecu.org/index.php?title=EcuFlash EcuFlash]

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec
==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII (96940011)===
===05 EDM VIII (96530006) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>2d972e4a9c0fde55e9ba4d5a967bd58eafdfbac9</sha1>
  </revision>
  <revision>
    <id>38</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T18:22:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8625" xml:space="preserve">The [[Mitsubishi Lancer Evolution]] has a powerful stock [[Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [http://openecu.org/index.php?title=EcuFlash EcuFlash]

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec
==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII (96940011)===
Stock 96940011 image: [[Image:96940011.HEX]]

===05 EDM VIII (96530006) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>ca8c803d41f5ff63d6a5c4250b3e18655508fbf7</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>User:EdwardMarshall</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>59</id>
    <parentid>57</parentid>
    <timestamp>2008-07-29T17:13:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="68" xml:space="preserve">I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.</text>
    <sha1>bc8db272730a753bdbbfd1fa7a5502c8822b9c5d</sha1>
  </revision>
  <revision>
    <id>60</id>
    <parentid>57</parentid>
    <timestamp>2008-07-29T17:38:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.

Quicklinks:
* [[Special:Specialpages]]</text>
    <sha1>a3ef7a9645ac3a26fb59d7e293b0ec9f75633b84</sha1>
  </revision>
  <revision>
    <id>58</id>
    <parentid>57</parentid>
    <timestamp>2008-07-29T17:59:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[User:EdwardMarshall]]" [edit=sysop:move=sysop]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.

Quicklinks:
* [[Special:Specialpages]]</text>
    <sha1>a3ef7a9645ac3a26fb59d7e293b0ec9f75633b84</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:96940011.HEX</title>
  <ns>6</ns>
  <id>3</id>
  <revision>
    <id>61</id>
    <timestamp>2008-07-29T18:21:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>USDM 2005 Mitsubishi Lancer Evolution ROM image</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">USDM 2005 Mitsubishi Lancer Evolution ROM image</text>
    <sha1>f3ce035a42b68be1c348eb89383d5551bb04d5e3</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Contents</title>
  <ns>12</ns>
  <id>4</id>
  <revision>
    <id>64</id>
    <parentid>62</parentid>
    <timestamp>2008-07-29T18:30:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1567" xml:space="preserve">{{PD Help Page}}
==Reading==
* [[Help:Navigation|Navigation]]
* [[Help:Searching|Searching]]
* [[Help:Tracking changes|Tracking changes]]
* [[Help:Watchlist|Watchlist]]

==Editing==
* [[Help:Editing pages|Editing pages]]
* [[Help:Starting a new page|Starting a new page]]
* [[Help:Formatting|Formatting]]
* [[Help:Links|Links]]
* [[Help:User page|User pages]]
* [[Help:Talk pages|Talk pages]]

===Advanced editing===
* [[Help:Images|Images]]
* [[Help:Tables|Tables]]
* [[Help:Categories|Categories]]
* [[Help:Subpages|Subpages]]
* [[Help:Managing files|Managing files]]
* [[Help:Moving a page|Moving a page]]
* [[Help:Redirects|Redirects]]
* [[Help:Deleting a page|Deleting a page]]
* [[Help:Protected pages|Protected pages]]

* [[Help:Templates|Templates]]
* [[Help:Variables|Variables]]
* [[Help:Namespaces|Namespaces]]

* [[Help:Special pages|Special pages]]
* [[Help:External searches|External searches]]

===Personal customization===
* [[Help:Preferences|Preferences]]
* [[Help:Skins|Skins]]

==Wiki administration==

* [[Help:Sysops and permissions|Sysops and permissions]]

The following features require extra permissions that are not normally granted to all wiki users.

* [[Help:Protecting and unprotecting pages|Protecting and unprotecting pages]]
* [[Help:Sysop deleting and undeleting|Sysop deleting and undeleting]]
* [[Help:Patrolled edits|Patrolled edits]]
* [[Help:Blocking users|Blocking users]]
* [[Help:Range blocks|Range IP blocks]]
* [[Help:Assigning permissions|Assigning permissions]]

{{Languages|Help:Contents}}
[[Category:Help| ]]
__NOTOC__</text>
    <sha1>5bf86078783a83dfdfb7dd81571ba2724eb9f91e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Navigation</title>
  <ns>12</ns>
  <id>5</id>
  <revision>
    <id>66</id>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6924" xml:space="preserve">{{PD Help Page}}
When viewing any page on a MediaWiki wiki, you'll find three main navigation elements:
# The [[#Sidebar|sidebar]] on the left gives you access to important pages in the wiki such as Recent changes or Upload file.
# At the top of the page are links (often called [[#Page Tabs|tabs]]) which relate to the page currently displayed: its associated discussion page, the version history, and&amp;mdash;most notably&amp;mdash;the edit link.
# In the top right corner you'll find [[#User Links|user links]]; as an anonymous user, you'll see a link to create an account or log in (they are the same page). As a logged-in user you have a collection of personal links, including ones to your user page and [[Help:Preferences|preferences]].
 
== Sidebar ==
[[Image:M-en-sidebar.png|framed|right|Example sidebar, shown on the left of the page]]
The sidebar is displayed on the left edge of the page below the site logo (if using the default MonoBook skin). This sidebar gives you access to important pages in the wiki such as Recent changes or Upload file. 

=== Navigation ===
Clicking on the logo brings you back to the main page of the wiki. The links in the navigation section just below will take you to important pages of the wiki. These links can be configured by site administrators.

{{Admin tip|tip=You can customize the navigation links by editing [[MediaWiki:Sidebar]]. Some entries call for separate MediaWiki: pages, e.g. to change the automatic link to the [[Main Page]] you would change [[MediaWiki:Mainpage]] (target page) and [[MediaWiki:Mainpage-text]] (displayed text). You can find a list of such pages via [[Special:Allmessages]]. For more information see [http://www.mediawiki.org/wiki/Manual:Interface/Sidebar Manual:Interface/Sidebar].}}

=== Toolbox ===
The toolbox contains a selection of links which change depending on what type of page you are viewing.

On all pages (except special pages):
* ''What links here'' takes you to a special page that lists the pages on this wiki which contain a link to the current page. This is helpful when you are looking for pages of related information. The ''What links here'' information can also be useful when you are refactoring wiki pages and need to check whether links to this page are still relevant after changes in the current page.
* The ''Related changes'' tool lists all recent changes in the pages linked to from the current page. Recent changes to all relevant template pages are included in the resulting page list. The "Hide minor edits" option that can be set in the user [[Help:Preferences|preferences]] applies, among other things, to ''Related Changes''.

On all pages (including special pages):
* ''Upload file'' displays a special page that allows logged-in users to upload images and other files to the wiki. Uploaded files can be linked from or embedded in wiki pages. Uploading files, viewing files on the server, including them in wiki pages and managing the uploaded files is discussed in the [[Help:Managing files|managing files]] section of this manual. This is not displayed if file uploading has been disabled or not enabled in the first place.
{{Admin tip|tip=To enable file uploading someone with access to the MediaWiki installation files needs to edit the &lt;code&gt;LocalSettings.php&lt;/code&gt; file and uncomment or add the option &lt;code&gt;$wgEnableUploads = true;&lt;/code&gt;. Uploaded files will be stored in the images folder specified by the &lt;code&gt;$wgUploadPath&lt;/code&gt; variable in the &lt;code&gt;LocalSettings.php&lt;/code&gt;. This directory must be writable if file uploads is enabled. The {{mediawiki|Manual:LocalSettings.php#Upload location|upload location}} and {{mediawiki|Manual:LocalSettings.php#Image uploads|image uploads}} settings are described in more detail on the MetaWiki {{mediawiki|Manual:LocalSettings.php|LocalSettings.php}} page.}}
* The ''Special pages'' tool lists the MediaWiki special pages. In MediaWiki terminology, a special page is one that presents information about the Wiki and/or allows access to administration activities for the wiki. For example, a list of users registered with the wiki, statistics about the wiki such as the number of pages and number of page edits, system logs, a list of orphaned pages, and so on. These special pages are commonly generated when the special page is loaded rather than being stored in the wiki database.

:''The function and use of the default special pages can be found in the [[Help:Special pages|special pages]] section of this manual.''

== Page Tabs ==
[[Image:M-en-pagetabs.png|framed|right|Default page tabs at the top of the page]]
The page tabs are displayed at the top of the article to the right of the site logo (if using the default MonoBook skin). These tabs allow you to perform actions or view pages that are related to the current article. The available default actions include: viewing, editing, and discussing the current article. The specific tabs displayed on your pages depend on whether or not you are logged into the wiki and whether you have sysop (administrator) privileges on the wiki. On special pages only the namespace tab is displayed.

;Default for all users
: ''[[Help:Namespaces|namespace]]'' (article, help, special page, template, user page etc.)
: ''discussion''
: ''edit'' (may read ''view source'' if anonymous editing is disabled, the page is in the MediaWiki: namespace, or the page is protected)
: ''history''

;Extra tabs for logged-in users:
: ''move''
: ''watch''

;Extra tabs for sysops:
: ''protect''
: ''delete''

Administrators can add or remove tabs by using JavaScript or installing extensions, so the tabs you see may be different depending on which wiki you are using.

== User Links ==
[[Image:M-en-userlinks.png|framed|right|Default user links at the top right of the page]]
The user links are displayed at the top far right of the article (if using the default MonoBook skin). These tabs allow the logged-in user to view and edit their user page and wiki preferences. Additionally, the user links allow the user to quickly access their contributions to the wiki and logout.

For anonymous users the user links is replaced by a link to the wiki login page or, if enabled, a link to your IP address and your IP address's talk page.

* ''&lt;username&gt;'' 
*: This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.
* ''my talk''
*: This links to your discussion page, where people can leave messages for you.
* ''preferences''
*: Allows you to change your personal site preferences.
* ''my watchlist''
*: A list of all pages that you are watching.  Pages can be added to this list by clicking ''watch'' at the top of the page.
* ''my contributions''
*: A list of all contributions you have made to the wiki.
* ''log out''
*: Click this link to log out of the wiki.

{{Languages|Help:Navigation}}
[[Category:Help|Navigation]]</text>
    <sha1>a3afb62b1282d0e3cf05ec5eae13acd67258604e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Searching</title>
  <ns>12</ns>
  <id>6</id>
  <revision>
    <id>69</id>
    <parentid>68</parentid>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2386" xml:space="preserve">{{PD Help Page}}
The quickest way to find information in MediaWiki is to look it up directly. On the left-hand side of your screen there is a '''Search''' box with two buttons under it labeled "Go" and "Search". 

&lt;div style="border:1px solid #ababff; background: #fdfdff; padding: 1em; margin: 1.1em 1em 1em 0em; font-size:105%"&gt;
Put your keyword in the searchbox.
* &lt;font face="MS Sans Serif,Arial"&gt;'''Go'''&lt;/font&gt; - (or ''Enter'' on keyboard) will take you automatically to the article, if it exists.
* &lt;font face="MS Sans Serif,Arial"&gt;'''Search'''&lt;/font&gt; - will search the text of all pages on the wiki (with some restrictions, see below).
&lt;/div&gt;

If you clicked 'search', or you clicked 'go' and the page you were looking for did not exist, you will be presented with a list of articles that matched your search criteria (or a message that no matches were found).  


== How it works ==
Here's how the search works:

* Only the article content is searched - the page title is ignored.
* The article content is searched in its raw (wikitext) form - i.e., it searches the text that appears in the edit box when you click 'edit', not the rendered page.  This means that content coming from an included template will not be picked up, but the target of piped links will be.
* Even if you enclose a phrase in quotes, the search looks for each word individually.  e.g., if you enter "world war 2" it will return pages that contain "world" and "war" and "2".
* The search is not case-sensitive, so "MediaWiki", "mediawiki" and "MEDIAWIKI" all give the same result.

== Restricting the search ==
If you click the 'Search' button without filling in anything, you will be taken to 'Special:Search' which gives you extra searching options (also available from any search results list)

You may find it useful to restrict a search to pages within a particular [[Help:Namespaces|namespace]] e.g., only search within the 'Talk' pages. Tick the namespaces you require for this search. 

By default only the [[Help:Namespaces|namespaces]] specified in your [[Help:Preferences|preferences]] will be searched.  Logged-in users can change their preferences to specify the namespaces they want to search by default. This can be done by selecting and deselecting boxes in the 'search' section of user preferences.

__NOTOC__
{{Languages|Help:Searching}}

[[Category:Help|Searching]]
[[Category:Search]]</text>
    <sha1>a55a2d7de4dbebc810a29b615be246ec81266b78</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Tracking changes</title>
  <ns>12</ns>
  <id>7</id>
  <revision>
    <id>71</id>
    <parentid>70</parentid>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2970" xml:space="preserve">{{PD Help Page}}
[[Image:M-en-recentchanges.png|thumb|370px|'''Recent changes''' shows the latest changes to articles, file uploads, deletions and page moves]]
MediaWiki offers a collection of special pages and tools to keep track of what is going on in the wiki. So you can watch for example:
* recent changes to all pages
* the revision history: all changes made to one page
* the contributions of one specific user 
* newly created pages

The most interesting special page is '''[[Special:Recentchanges]]'''. It displays all edits, file uploads, page moves, deletions and other actions done in the wiki. In the menu on top it offers a collection of links to customize your display: limit the number of changes shown, the number of days or restrict it to edits to a certain namespace. You can also hide edits marked as minor (don't forget that major changes can be flagged by a user as minor anyway).

One line in recent changes consists of several links:
* ''diff'' displays the difference to the previous revision of the page,
* ''hist'' links to the revision history of the page,
* the link with the full title of the page brings you to the current version. If the title is in bold, it indicates that it is on your [[Help:Watchlist|watchlist]].

Next is a flag describing the article modification type:
*''N'' denotes a new page,
*''m'' a minor edit,
*''b'' an edit made by a bot.


Following the timestamp, it shows the page size difference to the previous revision, then the user is mentioned, with a link to their [[Help:User page|user page]] and their [[Help:Talk pages#User Talk pages|talk page]] and contributions, or to their [[Help:Talk pages#User Talk pages|talk page]] only in the case of anonymous users.

Last but not least, there is an edit summary, appearing in italics, if the user submitted one when they made the edit.

=== Enhanced view ===
If you are logged in and have JavaScript enabled, you can also try the "enhanced" view. Simply go to your [[Help:Preferences#Recent changes|Preferences]] and enable "Enhanced recent changes (JavaScript)"; this will make recent changes show edits divided by page rather than being listed individually.  You will now see entries like the following:
:! 15:17 [[Main Page]] (4 changes; (+236) Page history) [Some User‎ (2×); Some Other User (2×)]
Simply click the blue arrow to the left of the page name and timestamp to expand that page's recent edits just as they were on the normal style. You can turn this enhancement on and off at will, so feel free to try both to see which one you prefer.

=== See also ===
* [[Special:Newpages]]
* Related changes: [[Special:Recentchangeslinked/Pagename]]
* User contributions: [[Special:Contributions/User]]
* History
* [[Special:Watchlist]]  

{{Admin tip|tip=You may want to add important pages in your wiki to [[MediaWiki:Recentchangestext]], the intro shown at [[Special:Recentchanges]]}}

{{Languages|Help:Tracking changes}}
[[Category:Help|Tracking changes]]</text>
    <sha1>626fbd9390403a2b51aa8ed80f83ee630bf8118d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Editing</title>
  <ns>12</ns>
  <id>8</id>
  <revision>
    <id>72</id>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="369" xml:space="preserve">{{PD Help Page}}
;Editing
:[[Help:Editing pages|Editing pages]]
:[[Help:Formatting|Formatting]]
:[[Help:Links|Links]]
:[[Help:Categories|Categories]]
;Advanced Editing
:[[Help:Images|Images]]
:[[Help:Tables|Tables]]
:[[Help:Templates|Templates]]
:[[Help:Variables|Variables]]
:[[Help:Managing files|Managing files]]

{{languages|Help:Editing}}
[[Category:Help|Editing]]</text>
    <sha1>cb8a7e354659712120513e7cca910c05831c5396</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Editing pages</title>
  <ns>12</ns>
  <id>9</id>
  <revision>
    <id>75</id>
    <parentid>74</parentid>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2577" xml:space="preserve">{{PD Help Page}}
It's very easy to edit the contents of a wiki. It only takes a few clicks.

* Click the '''edit''' [[Help:Navigation#Page Tabs|page tab]] at the top of the page.
* Make changes to the text.
* Click the '''Save page''' button.

Simple as that!

== Editing rules, editing conventions, and formatting ==

The number one rule of wiki editing, is to ''be bold''. Dive in and make changes. Other people can correct mistakes later, so have confidence, and give it a try! There can be all kinds of editing conventions, rules, and philosophy governing the editing of wiki pages, but the "be bold" rule overrides these!

In general try to write clearly and concisely and make sure you are always aiming to do something which improves the wiki contents. An edit might be to contribute whole paragraphs or pages full of information, or it could be as simple as fixing a typo or spelling mistake.

When you need to use some type of formatting e.g. new headings or '''bold''' text, you do this using wiki syntax. See [[Help:Formatting]] for some of the common types of formatting used.

== Edit Summary ==

Before you save a change, you can enter a short note in the '''Summary''' box describing your changes. Don't worry too much about this, or spend too much time thinking about it, but try to give a little description of what you just changed e.g. "''fixed typo''" or "''added more information about sunflowers''".

The summary gets stored alongside your edit, and allows people to [[Help:Tracking changes|track changes]] in the wiki more effectively.

== Preview ==

It's a good idea to use the 'Show preview' button to see what your change will look like, before you save it. This is also related to [[Help:Tracking changes|tracking changes]] because every time you save, this is displayed to others as a separate change. This isn't something to worry about too much, but it's good to get into the habit of eliminating mistakes in your own work, by using a preview before saving, rather than saving several minor corrections afterwards. 

== Other types of editing ==
With wiki edits you can start a new page, move (or rename) a page, or even delete a page:
* [[Help:Starting a new page]]
* [[Help:Moving a page]]
* [[Help:Deleting a page]]
Remember you should always aim to improve the overall contents of the wiki with your edits.

== Discussion ==
Every article has its own "talk page" where you can ask questions, make suggestions, or discuss corrections. See [[Help:Talk pages]] 

{{Languages|Help:Editing pages}}

[[Category:Edit]]
[[Category:Help|{{PAGENAME}}]]</text>
    <sha1>20fd7128ac9c863a113451bdc0496fbc8899241b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Starting a new page</title>
  <ns>12</ns>
  <id>10</id>
  <revision>
    <id>76</id>
    <timestamp>2008-07-29T18:30:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3004" xml:space="preserve">{{PD Help Page}}
There are several ways to start a new page.

== Using Wikilinks ==
MediaWiki makes it very easy to link wiki pages using a standard syntax (see [[Help:Links|Links]]). If you (or anyone else) creates a link to an article that doesn't exist yet, the link will be coloured red, &lt;span style="color: #ba0000"&gt;like this&lt;/span&gt;.

Clicking a red link, will take you to the edit page for the new article.  Simply type your text, click save and the new page will be created.

Once the page has been created, the link will change from &lt;span style="color: #ba0000"&gt;red&lt;/span&gt; to &lt;span style="color: #002bb8;"&gt;blue&lt;/span&gt; (&lt;span style="color: #5a3696;"&gt;purple&lt;/span&gt; for pages you've visited) indicating that the article now exists.

Usually this is the best way to create a new page, because it means that right from the start, the page will be linked from at least one other place on the wiki (and typically you will want to mesh it into other related pages later) If you are creating a new page without creating any link to it, you may need to ask yourself: Does this page really fit in with the topics already covered in the wiki? Also, how are you expecting visitors to find this page? Normally there is no reason to create a page without first creating a red link to it.

== Using the URL ==
You can use the wiki's URL for creating a new page. The URL to an article of the wiki is usually something like this:
*&lt;code&gt;&lt;nowiki&gt;http://www.example.net/index.php/&lt;/nowiki&gt;'''ARTICLE'''&lt;/code&gt; &amp;nbsp;&amp;nbsp; or
*&lt;code&gt;&lt;nowiki&gt;http://www.example.net/wiki/&lt;/nowiki&gt;'''ARTICLE'''&lt;/code&gt;

If you replace &lt;code&gt;'''ARTICLE'''&lt;/code&gt; with the name of the page you wish to create, you will be taken to a blank page which indicates that no article of that name exists yet. Clicking the "''edit''" [[Help:Navigation#Page Tabs|page tab]] at the top of the page will take you to the edit page for that article, where you can create the new page by typing your text, and clicking submit.

== From the search page ==
If you search for a page that doesn't exist (using the search box and 'go' button on the left of the page) then you will be provided with a link to create the new page.  (Note that this technique doesn't work if you use the 'search' button).

{{Admin tip|tip=The "{{mediawiki|Extension:Inputbox|inputbox extension}}" allows you to provide an even easier way for your users to create new pages}}

== Create redirects to your new page == 
Don't forget to setup redirects when you create a page. If you think another person may search for the page you've created by using a different name or spelling, please create the proper redirect(s). See [[Help:Redirects]]

== Protecting your new page ==
Normally a new wiki page can be edited by other people (that ''is'' one of the main ideas of a wiki!)  However, you could 'protect' the page, if desired, to prevent normal users from editing it. This requires sysop permissions.

{{Languages|Help:Starting a new page}}

[[Category:Help|Starting a new page]]</text>
    <sha1>bc8d72bc1217dbb4f41ee0e2fb2488b32031c3b5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Formatting</title>
  <ns>12</ns>
  <id>11</id>
  <revision>
    <id>79</id>
    <parentid>78</parentid>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5665" xml:space="preserve">{{PD Help Page}}
You can format your text using wiki markup. This consists of normal characters like asterisks, single quotes or equation marks which have a special function in the wiki, sometimes depending on their position. For example, to format a word in ''italic'', you include it in two single quotes like &lt;tt&gt;&lt;nowiki&gt;''this''&lt;/nowiki&gt;&lt;/tt&gt;

== Text formatting markup ==

{| align="center" {{Prettytable}}
|-
|{{Hl2}} |'''Description'''
|{{Hl2}} |'''You type'''	
|{{Hl2}} |'''You get'''
|-
| colspan="3" align="center" | ''applies anywhere''
|-
|Italic text
|&lt;tt&gt;&lt;nowiki&gt;''italic''&lt;/nowiki&gt;&lt;/tt&gt;
|''italic''
|-
| Bold text
|&lt;tt&gt;&lt;nowiki&gt;'''bold'''&lt;/nowiki&gt;&lt;/tt&gt;
|'''bold'''
|-
| Bold and italic
|&lt;tt&gt;&lt;nowiki&gt;'''''bold &amp; italic'''''&lt;/nowiki&gt;&lt;/tt&gt;
|'''''bold &amp; italic'''''
|-
|Escape wiki markup
|&lt;tt&gt;&lt;nowiki&gt;&lt;nowiki&gt;no ''markup''&lt;/nowiki&gt;&lt;/nowiki&gt;&lt;/tt&gt;
|&lt;nowiki&gt;no ''markup''&lt;/nowiki&gt;
|-
|Fixed width text
|
&lt;nowiki&gt;&lt;tt&gt;Fixed width text&lt;/tt&gt;&lt;/nowiki&gt;
|
&lt;tt&gt;Fixed width text&lt;/tt&gt;
|-
| colspan="3" align="center" | ''only at the beginning of the line''
|-
| Indent text
|
&lt;tt&gt;&lt;nowiki&gt;:Single indent&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;::Double indent&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;:::::Multiple indent&lt;/nowiki&gt;&lt;/tt&gt;
|
:Single indent
::Double indent
:::::Multiple indent
|-
|Headings of&lt;br /&gt;
different levels &lt;ref&gt;An article with four or more headings will automatically create a [http://en.wikipedia.org/wiki/Wikipedia:Section#Table_of_contents_.28TOC.29 table of contents].&lt;/ref&gt;
|
&lt;tt&gt;&lt;nowiki&gt;=level 1=&lt;/nowiki&gt;&lt;/tt&gt;&lt;ref&gt;Use of a level 1 heading is '''''highly discouraged''''' as it appears with the same formatting and size as the page title, which can be confusing.&lt;/ref&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;==level 2==&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;===level 3===&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;====level 4====&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;=====level 5=====&lt;/nowiki&gt;&lt;/tt&gt;&lt;br /&gt;
&lt;tt&gt;&lt;nowiki&gt;======level 6======&lt;/nowiki&gt;&lt;/tt&gt;
|
&lt;!-- little hack to prevent TOC viewing --&gt;
&lt;span style="font-size: 188%; margin: 0; padding-top: .5em; padding-bottom: .17em; border-bottom: 1px solid #aaa;"&gt;Level 1&lt;/span&gt;&lt;br/&gt;&lt;br/&gt;
&lt;span style="font-size: 150%; margin: 0; padding-top: .5em; padding-bottom: .17em; border-bottom: 1px solid #aaa;"&gt;Level 2&lt;/span&gt;&lt;br/&gt;&lt;br/&gt;
&lt;span style="font-size: 132%; border-bottom: none; font-weight: bold;"&gt;Level 3&lt;/span&gt;&lt;br/&gt;
&lt;span style="font-size: 100%; border-bottom: none; font-weight: bold;"&gt;Level 4&lt;/span&gt;&lt;br/&gt;
{{DEFAULTSORT:[[[http://www.example.com link title]]#Redirect [[—[[Category:]]]]]}}&lt;span style="font-size: 86%; border-bottom: none; font-weight: bold;"&gt;Level 5&lt;/span&gt;&lt;br/&gt;
&lt;span style="font-size: 80%; border-bottom: none; font-weight: bold;"&gt;Level 6&lt;/span&gt;&lt;br/&gt;
|-
|Horizontal rule
|
&lt;tt&gt;&lt;nowiki&gt;----&lt;/nowiki&gt;&lt;/tt&gt;
|
----
|-
|Bullet list
|
&amp;#42; one&lt;br&gt;
&amp;#42; two&lt;br&gt;
&amp;#42; three&lt;br&gt;
&amp;#42;&amp;#42; three and one-third&lt;br&gt;
&amp;#42;&amp;#42; three and two-thirds&lt;br&gt;
|
* one
* two
* three
** three and one-third
** three and two-thirds
|-
|Numbered list
|
&amp;#35; one&lt;br /&gt;
&amp;#35; two&lt;nowiki&gt;&lt;br&gt;&lt;/nowiki&gt;spanning several lines&lt;nowiki&gt;&lt;br&gt;&lt;/nowiki&gt;without breaking the numbering&lt;br /&gt;
&amp;#35; three&lt;br /&gt;
&amp;#35;&amp;#35; three point one&lt;br /&gt;
&amp;#35;&amp;#35; three point two&lt;br /&gt;
|
# one
# two&lt;br&gt;spanning several lines&lt;br&gt;without breaking the numbering
# three
## three point one
## three point two
|-
| Mixture of bulleted&lt;br /&gt; and numbered lists
|
&amp;#35; one&lt;br /&gt;
&amp;#35; two&lt;br /&gt;
&amp;#35;&amp;#42; two point one&lt;br /&gt;
&amp;#35;&amp;#42; two point two&lt;br /&gt;
|
# one
# two
#* two point one
#* two point two
|-
|Definition list
|
&amp;#59;Definition&lt;br /&gt;
&amp;#58;item 1&lt;br /&gt;
&amp;#58;item 2&lt;br /&gt;
|
;Definition
:item 1
:item 2
|-
|Preformatted text
|
&amp;nbsp;&amp;nbsp;preformatted text is done with&lt;br /&gt;
&amp;nbsp;&amp;nbsp;a space at the&lt;br /&gt;
&amp;nbsp;&amp;nbsp;beginning of the line&lt;br /&gt;
|
 preformatted text is done with
 a space at the 
 beginning of the line
|-
|Preformatted text with no indentation
|
&amp;nbsp;&lt;nowiki&gt;&lt;pre&gt; some preformatted text with no indentation &lt;/pre&gt;&lt;/nowiki&gt;
|
&lt;pre&gt;
some preformatted
text with no indentation
&lt;/pre&gt;
|-
|Blockquotes
|
Body&lt;br&gt;
text text text text text text text text text text text text
text text text text text text text text text text text text

&lt;nowiki&gt;&lt;blockquote&gt;  quote quote quote quote quote quote &lt;/blockquote&gt;&lt;/nowiki&gt;

text text text text text text text text text text text text
|
Body&lt;br&gt;
text text text text text text text text text text text text
text text text text text text text text text text text text

&lt;blockquote&gt;  quote quote quote quote quote quote &lt;/blockquote&gt;

text text text text text text text text text text text text

|-
|Comment
|
&lt;tt&gt;&lt;nowiki&gt;&lt;!--This is comment--&gt;&lt;/nowiki&gt;&lt;/tt&gt;
|
&lt;!--This is comment--&gt;|}


Notes: &lt;references/&gt;

== Paragraphs ==

MediaWiki ignores normal line breaks. To start a new paragraph, leave an empty line. You can also start a new line with the HTML tags &lt;tt&gt;&lt;nowiki&gt;&lt;br&gt; or &lt;br/&gt;&lt;/nowiki&gt;&lt;/tt&gt;.

== HTML ==

Some [[wikipedia:HTML|HTML]] tags are allowed in MediaWiki, for example &lt;tt&gt;&lt;nowiki&gt;&lt;code&gt;&lt;/nowiki&gt;&lt;/tt&gt;, &lt;tt&gt;&lt;nowiki&gt;&lt;div&gt;&lt;/nowiki&gt;&lt;/tt&gt;, &lt;tt&gt;&lt;nowiki&gt;&lt;span&gt;&lt;/nowiki&gt;&lt;/tt&gt; and &lt;tt&gt;&lt;nowiki&gt;&lt;font&gt;&lt;/nowiki&gt;&lt;/tt&gt;.

{{Admin tip|tip=If you trust your users you can allow full HTML by setting &lt;code&gt;{{mediawiki|Manual:$wgRawHtml|$wgRawHtml}} = true;&lt;/code&gt; in {{mediawiki|Manual:LocalSettings.php|LocalSettings.php}}.}}


== Other formatting ==
Beyond the text formatting markup shown above, here are some other formatting references:
*[[Help:Links|Links]]
*[[Help:Images|Images]]
*[[Help:Tables|Tables]]
*[http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_Page_Help/Do-It-Yourself/Formatting_Text More Formatting from Wikipedia]

{{Languages|Help:Formatting}}

[[Category:Help|Formatting]]</text>
    <sha1>24fecc58e3753aa9d358a8cd7c87f5f567f863e1</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Links</title>
  <ns>12</ns>
  <id>12</id>
  <revision>
    <id>81</id>
    <parentid>80</parentid>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5208" xml:space="preserve">{{PD Help Page}}
There are four sorts of links in MediaWiki: 
# internal links to other pages in the wiki
# external links to websites
# [[#Interwiki links|interwiki links]] (links to other wikis)
# inter-language links to other language versions of the same wiki

To add an internal link, enclose the name of the page you want to link to in double square brackets. When you save the page, you'll see the new link pointing to your page. If the page exists already, it is displayed in blue, empty pages are displayed in red. Selflinks to the current page are not transformed in URLs but displayed in bold.

The first letter of the target page is automatically capitalized and spaces are represented as underscores (typing an underscore in the link will have a similar effect as typing a space, but is not recommended, since the underscore will also be shown in the text).

== How to link ==
{| {{Prettytable}}
|-
|{{Hl3}}|'''Description'''
|{{Hl3}}|'''You type'''	
|{{Hl3}}|'''You get'''
|-
|Internal link
|&lt;tt&gt;&lt;nowiki&gt;[[Main Page]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[Main Page]]
|-
|Piped link 
|&lt;tt&gt;&lt;nowiki&gt;[[Main Page|different text]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[Main Page|different text]]
|-
|External link
|&lt;tt&gt;&lt;nowiki&gt;http://mediawiki.org&lt;/nowiki&gt;&lt;/tt&gt;
|http://mediawiki.org
|-
|External link,&lt;br /&gt;
different title
|&lt;tt&gt;&lt;nowiki&gt;[http://mediawiki.org MediaWiki]&lt;/nowiki&gt;&lt;/tt&gt;
|[http://mediawiki.org MediaWiki]
|-
|External link,&lt;br /&gt;
numbered
|&lt;tt&gt;&lt;nowiki&gt;[http://mediawiki.org]&lt;/nowiki&gt;&lt;/tt&gt;
|[http://mediawiki.org]
|-
|Anchor link 
|&lt;tt&gt;&lt;nowiki&gt;[[#See also]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[#See also]]
|-
|Anchor link at another page
|&lt;tt&gt;&lt;nowiki&gt;[[Help:Images#See also]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[Help:Images#See also]]
|-
|Category link
|&lt;tt&gt;&lt;nowiki&gt;[[:Category:Help]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[:Category:Help]]
|-
|Internal link to image file
|&lt;tt&gt;&lt;nowiki&gt;[[media:example.jpg]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[media:example.jpg]]
|-
|Interwiki link
|&lt;tt&gt;&lt;nowiki&gt;[[Wikipedia:MediaWiki]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[Wikipedia:MediaWiki]]
|-
|mailto link
|&lt;tt&gt;&lt;nowiki&gt;[mailto:info@example.org email me]&lt;/nowiki&gt;&lt;/tt&gt;
|[mailto:info@example.org email me]
|-
|redirect
|&lt;tt&gt;&lt;nowiki&gt;#REDIRECT [[Main Page]]&lt;/nowiki&gt;&lt;/tt&gt;
| &amp;rarr; [[Main Page]]
|}

=== More advanced ===

{| {{Prettytable}}
|-
|{{Hl3}}|'''Description'''
|{{Hl3}}|'''You type'''	
|{{Hl3}}|'''You get'''
|-
|Piped link,&lt;br /&gt;
different title
|&lt;tt&gt;&lt;nowiki&gt;[[Main Page|&lt;span title="different title"&gt;different text&lt;/span&gt;]]&lt;/nowiki&gt;&lt;/tt&gt;
|[[Main Page|&lt;span title="different title"&gt;different text&lt;/span&gt;]]
|-
|External link,&lt;br /&gt;
same host unnamed
|&lt;tt&gt;&lt;nowiki&gt;[http://{{SERVERNAME}}/pagename]&lt;/nowiki&gt;&lt;/tt&gt;
|[http://{{SERVERNAME}}/pagename]
|-
|mailto named with subject line and body
|&lt;tt&gt;&lt;nowiki&gt;[mailto:info@example.org?Subject=URL%20Encoded%20Subject&amp;body=Body%20Text info]&lt;/nowiki&gt;&lt;/tt&gt;
|[mailto:info@example.org?Subject=URL%20Encoded%20Subject&amp;body=Body%20Text info]
|}


----

{{admin tip|tip=
Which protocols (like http:) are allowed for links is controlled by the [http://www.mediawiki.org/wiki/Manual:%24wgUrlProtocols $wgUrlProtocols]&lt;!-- deliberate use of http url, these pages get exported. Should these admin tips even be here? This is supposed to be end user help is it not? --&gt; setting. 
}}

{{admin tip|tip=
To remove the 'external link image' from next to each of the external links, add the following to the page located at &lt;code&gt;MediaWiki:Monobook.css&lt;/code&gt; on your wiki.

&lt;pre&gt;
#bodyContent a.external,
#bodyContent a[href ^="gopher://"] {
        background: none;
        padding-right: 0;
}
&lt;/pre&gt;
}}

== How to avoid auto-links ==

By default, when you write a URL as is, it will be transformed in an external link.

To avoid that effect, put the URL between &amp;lt;nowiki&amp;gt; start &amp; end tags as in:

 &amp;lt;nowiki&amp;gt;&lt;nowiki&gt;http://mediawiki.org&lt;/nowiki&gt;&amp;lt;/nowiki&amp;gt;


== Interwiki links ==
Interwiki links are links from the local wiki to another wiki. For example you can link to the Sunflower article on wikipedia.org by typing &lt;tt&gt;&lt;nowiki&gt;[[wikipedia:Sunflower]]&lt;/nowiki&gt;&lt;/tt&gt;. This results in a link like this: [[wikipedia:Sunflower]]

Similar to internal page links, you can create piped links, with alternate link text. e.g. &lt;tt&gt;&lt;nowiki&gt;[[wikipedia:Sunflower|big yellow flower]]&lt;/nowiki&gt;&lt;/tt&gt;

Basically this is an abbreviation for longer URLs. A very similar link could be created as a normal external link by typing &lt;tt&gt;&lt;nowiki&gt;[http://en.wikipedia.org/wiki/Sunflower Sunflower]&lt;/nowiki&gt;&lt;/tt&gt;, but interwiki links allow you to type out an easy and compact link, almost as if you are linking to a page on your own wiki.

Some interesting things to note:
* Interwiki links are displayed slightly differently to external links, without the little external link icon.
* Complex page names with spaces and other characters are handled elegantly, just as they would be for an internal page link, making this more tidy than creating an external link to a full URL. For example &lt;tt&gt;&lt;nowiki&gt;[[wikipedia:Sunflower County, Mississippi]]&lt;/nowiki&gt;&lt;/tt&gt; is in some ways tidier and more elegant than the full URL : &lt;tt&gt;http://en.wikipedia.org/wiki/Sunflower_County%2C_Mississippi&lt;/tt&gt;

== See also ==
* [[Help:Linked images|Linked images]]
 
{{Languages|Help:Links}}

[[Category:Help|Links]]
[[Category:Link]]</text>
    <sha1>3cb87a58a3419d8b10dd39bf8a2cb37c8e87f7d8</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Categories</title>
  <ns>12</ns>
  <id>14</id>
  <revision>
    <id>85</id>
    <parentid>84</parentid>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3588" xml:space="preserve">{{PD Help Page}}

MediaWiki allows you to categorize pages by adding one or more category tags to the text.  Adding these tags create links at the bottom of the article which take you to the list of all pages in that category, which makes it easy to browse related articles.

== How to add categories ==

To add an article to a category put the following at the end of the page you are editing...

 &lt;nowiki&gt;[[Category:NAME]]&lt;/nowiki&gt;

where NAME is the name of the category you want to add it to.  Any number of category tags may be added to the page - the page will be listed in all of them.

You can also specify an additional SORT parameter that dictates where the page will appear, alphabetically, within the category. This is achieved by using the following markup:

 &lt;nowiki&gt;[[Category:NAME|SORT]]&lt;/nowiki&gt;

So for example, to add this page to the 'Help' category, you would use:

 &lt;nowiki&gt;[[Category:Help|Categories]]&lt;/nowiki&gt;

Note that we used 'Categories' as the sort parameter.  Without this the page would be listed under 'H' for 'Help:Categories',  instead of under 'C', which is more useful.  Other situations where you might want to use the sort parameter is when you have articles about people that are titled as &lt;code&gt;FirstName LastName&lt;/code&gt; but within the category you want them listed as &lt;code&gt;LastName, FirstName&lt;/code&gt;.

Another way to sort the article in the correct letter without the namespace is

 &lt;nowiki&gt;[[Category:Help|{{SUBPAGENAME}}]]&lt;/nowiki&gt;

This is extremely helpful when using templates which include a category tag. ...

''Note: the SORT parameter does '''not''' affect how the page title is displayed within the category listing, just how it is ordered.  In the above example, the link to this page will still be 'Help:Categories', and not 'Categories' as you might expect!''

== Linking to Category Pages ==

To create a link to a category page:

 &lt;nowiki&gt;[[:Category:NAME]]&lt;/nowiki&gt;

If you were linking to the Category Page for Help on MediaWiki, the link would look like this: [[:Category:Help]]

If you want to display alternate text for the link:

 &lt;nowiki&gt;[[:Category:NAME|TEXT]]&lt;/nowiki&gt;

Here is an example of the same link to the Category Page for Help on MediaWiki as above, but with alternative text: [[:Category:Help|MediaWiki Help Index]]

== Categorize Categories==

Categories themselves and other uploaded files like Pictures can be categorized exactly like normal pages. It is useful to connect the article-categories with categories already in place to establish connections and hierarchies. To this end, after saving the article, follow the category links at the end of the page to see, if the category is already in place and if not, categorize them until you connect them with an existing category.

==Moving categories==
Categories cannot be easily moved [[Help:Moving a page|like other pages]]. For this reason, category names should be chosen carefully.

The easiest way (for those with admin privileges) is to create the new page, delete the old one, and then change the tags in each member of the category (manually or with a bot). However, this loses the page history - not a huge problem when categories are used only for navigation, but when a wiki is structured differently and the category pages contain significant amounts of text, this is undesirable.

=== Moving with revision history ===
However, category pages ''can'' be moved together with the full revision history, with some effort, by using the [[Special:Export]] and [[Special:Import]] functions.

{{Languages|Help:Categories}}
[[Category:Help|Categories]]</text>
    <sha1>0c0c9e13d0649d8049d54effed8beaf9ca20c339</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Images</title>
  <ns>12</ns>
  <id>15</id>
  <revision>
    <id>86</id>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3861" xml:space="preserve">{{PD Help Page}}

This page explains the image syntax when editing the wiki. Before using images, you must {{mediawiki|Manual:Configuring_file_uploads|configure file uploads}} and [[Help:Managing files|upload a file]].

__TOC__
{| {{Prettytable}}
|-
|{{Hl3}}|'''Description'''
|{{Hl3}}|'''You type''' 
|{{Hl3}}|'''You get'''
|-
|Embed image&lt;br /&gt; (with alt text)
|
&lt;code&gt;&lt;nowiki&gt;[[Image:Example.jpg|Sunflowers]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[Image:Example.jpg|Sunflowers]]
|-
|Link to description page
|
&lt;code&gt;&lt;nowiki&gt;[[:Image:Example.jpg]]&lt;/nowiki&gt;&lt;/code&gt;&lt;br /&gt;
&lt;code&gt;&lt;nowiki&gt;[[:Image:Example.jpg|Sunflowers]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[:Image:Example.jpg]]&lt;br /&gt;
[[:Image:Example.jpg|Sunflowers]]
|-
|Link directly to file
|
&lt;code&gt;&lt;nowiki&gt;[[Media:Example.jpg]]&lt;/nowiki&gt;&lt;/code&gt;&lt;br /&gt;
&lt;code&gt;&lt;nowiki&gt;[[Media:Example.jpg|Sunflowers]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[Media:Example.jpg]]&lt;br /&gt;
[[Media:Example.jpg|Sunflowers]]
|-
|Thumbnail&lt;br /&gt; (centered, 100 pixels&lt;br /&gt; wide, with caption)
|
&lt;code&gt;&lt;nowiki&gt;[[Image:Example.jpg|center|thumb|100px|Sunflowers]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[Image:Example.jpg|center|thumb|100px|Sunflowers]]
|-
|Border&lt;br /&gt; (100 pixels) &lt;br /&gt; Results in a very small gray border
&lt;!-- Note: because the fine gray border can not be seen when used on Image:Exaple.jpg (sunflowers image), an image with a white background is used --&gt;
|
&lt;code&gt;&lt;nowiki&gt;[[Image:Example-white-bg.jpg|border|100px]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[Image:Example-white-bg.jpg|border|100px]]
|-
|Frameless&lt;br /&gt;Like thumbnail, respect user preferences for image width but without border and no right float.
|
&lt;code&gt;&lt;nowiki&gt;[[Image:Example.jpg|frameless]]&lt;/nowiki&gt;&lt;/code&gt;
|
[[Image:Example.jpg|frameless]]
|}

== Syntax ==
The full syntax for displaying an image is:
 &lt;code&gt;&lt;nowiki&gt;[[Image:{name}|{options}]]&lt;/nowiki&gt;&lt;/code&gt;
Where options can be zero or more of the following, separated by pipes:
*&lt;code&gt;thumb&lt;/code&gt;, &lt;code&gt;thumbnail&lt;/code&gt;, or &lt;code&gt;frame&lt;/code&gt;: Controls how the image is formatted
*&lt;code&gt;left&lt;/code&gt;, &lt;code&gt;right&lt;/code&gt;, &lt;code&gt;center&lt;/code&gt;, &lt;code&gt;none&lt;/code&gt;: Controls the alignment of the image on the page
*&lt;code&gt;{width}px&lt;/code&gt;: Resizes the image to the given width in pixels
*&lt;code&gt;{caption text}&lt;/code&gt;
* Special cases:
** &lt;code&gt;page=1&lt;/code&gt;: displays the specified page when showing a djvu file.

The options can be given in any order. If a given option does not match any of the other possibilities, it is assumed to be the caption text. Caption text can contain wiki links or other formatting.

== Other files ==
You can link to an external file using the same syntax used for linking to an external web page. 
*&lt;code&gt;&lt;nowiki&gt;[http://url.for/some/image.png]&lt;/nowiki&gt;&lt;/code&gt;
Or with different text:
*&lt;code&gt;&lt;nowiki&gt;[http://url.for/some/image.png link text here]&lt;/nowiki&gt;&lt;/code&gt;

If it is enabled on your wiki (see {{mediawiki|Manual:$wgAllowExternalImages}}), you can also embed external images. To do that, simply insert the image's url:
*&lt;code&gt;&lt;nowiki&gt;http://url.for/some/image.png&lt;/nowiki&gt;&lt;/code&gt;

== Gallery of images ==
It's easy to make a gallery of thumbnails with the &lt;code&gt;&lt;nowiki&gt;&lt;gallery&gt;&lt;/nowiki&gt;&lt;/code&gt; tag. The syntax is:
&lt;pre&gt;
&lt;gallery&gt;
Image:{filename}|{caption}
Image:{filename}|{caption}
{...}
&lt;/gallery&gt;
&lt;/pre&gt;
Captions are optional, and may contain wiki links or other formatting.

for example:
&lt;pre&gt;
&lt;gallery&gt;
Image:Example.jpg|Item 1
Image:Example.jpg|a link to [[Help:Contents]]
Image:Example.jpg
Image:Example.jpg
Image:Example.jpg|''italic caption''
&lt;/gallery&gt;
&lt;/pre&gt;
is formatted as:
&lt;gallery&gt;
Image:Example.jpg|Item 1
Image:Example.jpg|a link to [[Help:Contents]]
Image:Example.jpg
Image:Example.jpg
Image:Example.jpg|''italic caption''
&lt;/gallery&gt;

== See also ==
* [[Help:Linked images|Linked images]]

==External Link==
* [[wikipedia:Project:Extended image syntax|Wikipedia:Extended image syntax]]

{{Languages|Help:Images}}

[[Category:Help|Images]]</text>
    <sha1>867ed358c470a504beec5c4c6153fc86e01090d8</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Subpages</title>
  <ns>12</ns>
  <id>16</id>
  <revision>
    <id>88</id>
    <timestamp>2008-07-29T18:30:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2265" xml:space="preserve">{{PD Help Page}}
'''Subpages''' introduce some hierarchical organisation into wiki page names, with levels of the hierarchy separated by slashes '/'.

=== Namespaces ===
MediaWiki's '''subpage''' feature is turned '''off by default''' in the main namespace, but can be used on [[Help:Talk pages|talk pages]] and [[Help:User page|user pages]]. See [[Help:namespaces]]. In namespaces where the feature is switched off, any slashes (/) within a page name are simply part of the page name and do nothing special.

=== Slashes within a page name ===
Slashes (/) within a page name break the page into parent and subpages, recursively, eg:

:[[Example page]]
:[[Example page/Some sub-page]]
:[[Example page/Some sub-page/Some sub-sub-page]]

A '''link back to parent''' will automatically appear at the top of each subpage. In the case of sub-sub-pages, a set of breadcrumb navigation links will automatically be presented. Note that these links do not appear, however, if the parent page has not yet been created.

=== Using (and over-using) sub pages ===
There are various uses for the subpage mechanism. The main two intended uses are:
* On a [[Help:Talk pages|talk page]] create a subpage (or several) for an archiving of old discussions
* On a [[Help:User page|user page]] create a subpage (or several) to use as a scratchpad editing space.

People instinctively think hierarchically when trying to organise information, so it may be tempting use subpages all the time, however, subpages can be over-used. Remember that having a page name with a slash will generally make the name longer, harder to remember, and thus more difficult to link to. Some people find it more elegant to keep page naming simple. By sticking to a flat naming structure, with a manually maintained web of wiki links, a structure will emerge organically (and this can include a pseudo-hierarchy)

{{Admin tip|tip=Subpages can be activated within the 'main' namespace by adding to the {{mediawiki|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}} array.}}

==See also==
* [[Meta:Help:Link#Subpage feature]]
* [[Help:Variables#Page names]]
* {{mediawiki|Manual:$wgNamespacesWithSubpages}}

[[Category:Help|{{PAGENAME}}]]
[[Category:Subpage|{{PAGENAME}}]]

{{languages|Help:Subpages}}</text>
    <sha1>2c35cefee8b901b451df5efcab383dd3dbb55b13</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Templates</title>
  <ns>12</ns>
  <id>17</id>
  <revision>
    <id>91</id>
    <parentid>90</parentid>
    <timestamp>2008-07-29T18:30:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5608" xml:space="preserve">{{PD Help Page}}
If you have standard texts you want to include on several pages, the MediaWiki template feature comes into play (like the tag above which is included in the pages of the Help namespace).

==Creating a template==
Template names are prefixed with &lt;code&gt;Template:&lt;/code&gt;, you [[Help:Starting a new page|create them like any other wiki page]].

==Using a template==
Templates are wiki pages which can be used in other pages in three ways:
*&lt;code&gt;&lt;nowiki&gt;{{Name}}&lt;/nowiki&gt;&lt;/code&gt; 'transcludes' (i.e. includes a copy) the content of the template (stored in the page &lt;nowiki&gt;[[Template:Name]]&lt;/nowiki&gt;) whenever the page containing the template transclusion is fetched and displayed; i.e. if the template is later changed, the displayed transcluding page will automatically change too
*&lt;code&gt;&lt;nowiki&gt;{{subst:Name}}&lt;/nowiki&gt;&lt;/code&gt; replaces that string with the contents of the template, in the source of the transcluding page, when you save that page; the copy of the template contents can then be edited normally (and separately from the original in the template page). '''''Note''''': don't use this if you are looking to continually propogate changes from the source template to the page(s) that references it.
*&lt;code&gt;&lt;nowiki&gt;{{msgnw:Name}}&lt;/nowiki&gt;&lt;/code&gt; includes the template in a form that displays it as raw wiki syntax (the way &lt;code&gt;&lt;nowiki&gt;&amp;lt;nowiki&amp;gt;&lt;/nowiki&gt;&lt;/code&gt; does) when the page containing it is fetched

==Using parameters in templates==
&lt;div style="float:right; margin:8px;"&gt;
{| {{Prettytable}} 
|-
|{{Hl2}} colspan="2" align="center" |'''Template with numbered parameters'''	
|-
| colspan="2" |
&lt;pre&gt;&lt;nowiki&gt; 
'''A little thank you...'''&lt;br&gt;
&lt;small&gt;for {{{1}}}.&lt;br&gt;
hugs, {{{2}}}&lt;/small&gt;
&lt;/nowiki&gt;&lt;/pre&gt; 
|-
|{{Hl2}}|'''You type'''	
|{{Hl2}}|'''You get'''
|-
|&lt;code&gt;&lt;nowiki&gt;{{Thankyou|all your hard work|Joe}}&lt;/nowiki&gt;&lt;/code&gt;
|
{{Thankyou|all your hard work|Joe}}
|-
|{{Hl2}} colspan="2" align="center" |'''with named parameters'''	
|-
| colspan="2" |
&lt;pre&gt;&lt;nowiki&gt; 
'''A little thank you...'''&lt;br&gt;
&lt;small&gt;for {{{reason}}}.&lt;br&gt;
hugs, {{{signature}}}&lt;/small&gt;
&lt;/nowiki&gt;&lt;/pre&gt; 
|-
|{{Hl2}}|'''You type'''	
|{{Hl2}}|'''You get'''
|-
|&lt;pre&gt;&lt;nowiki&gt;{{Thankyou
|reason=all your hard work
|signature=Joe}}&lt;/nowiki&gt;&lt;/pre&gt;
|
{{Thankyou|all your hard work|Joe}}
|}
&lt;/div&gt;
You can define parameters in templates either numbered as &lt;code&gt;&lt;nowiki&gt;{{{1}}}&lt;/nowiki&gt;&lt;/code&gt; or named &lt;code&gt;&lt;nowiki&gt;{{{param}}}&lt;/nowiki&gt;&lt;/code&gt;.  

'''Example:''' You want a little thank you note you can put on the talk page of other users. It will contain a reason and your signature. You could create [[Template:Thankyou]] to enter your text, as in the example in the table.

When using the template on a page, you fill in the parameter values, separated by a pipe char (|): &lt;code&gt;&lt;nowiki&gt;{{Thankyou|all your hard work|Joe}}&lt;/nowiki&gt;&lt;/code&gt;.  For named parameters use "name=value" pairs separated by a pipe char:   &lt;code&gt;&lt;nowiki&gt;{{Thankyou|reason=all your hard work|signature=Joe}}&lt;/nowiki&gt;&lt;/code&gt;. The advantage of using named parameters in your template is that they are flexible in order. It also makes the template easier to understand if you have many parameters. If you want to change the order of numbered parameters, you have to mention them explicitly: &lt;code&gt;&lt;nowiki&gt;{{Thankyou|2=Joe|1=all your hard work}}&lt;/nowiki&gt;&lt;/code&gt;.

You can also provide default values for parameters, i.e. values that are going to be used if no value is provided for a parameter. For example, &lt;code&gt;&lt;nowiki&gt;{{{reason|all your hard work}}}&lt;/nowiki&gt;&lt;/code&gt; would result in ''"all your hard work"'' if no value was provided for the parameter &lt;tt&gt;reason&lt;/tt&gt;.

==Control template inclusion==
You can control template inclusion by the use of &lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt; and
&lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt; tags.

Anything between &lt;code&gt;&lt;nowiki&gt;&lt;noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/code&gt; will be processed and
displayed only when the page is being viewed directly, not included.

Possible applications are:
* Categorising templates
* Interlanguage links to similar templates in other languages
* Explanatory text about how to use the template

The converse is &lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt;. Text between &lt;code&gt;&lt;nowiki&gt;&lt;includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt; and
&lt;code&gt;&lt;nowiki&gt;&lt;/includeonly&gt;&lt;/nowiki&gt;&lt;/code&gt; will be processed and displayed only when the page is
being included. The obvious application is to add all pages containing a given template to a [[Help:Categories|category]], without putting the template itself into that category.

'''Note:''' when you change the categories applied by a template, the categorization of the pages that use that template may not be updated until some time later: this is handled by the {{mediawiki|Manual:Job_queue|job queue}}.

==Organizing templates==
For templates to be effective users need to find them and be able to use them. A simple technique is to include an example on the template page.
For example:
&lt;div style="display:table; width:auto;"&gt;&lt;pre&gt;
&lt;noinclude&gt;
==Usage==
Allows to establish a link to a subject:
{{NameOfTemplate|Term1+Term2+Term3}}
&lt;/noinclude&gt;
&lt;/pre&gt;&lt;/div&gt;

Then, an editor can simply copy and paste the example to create a similar page.

==See Also==
*[[Help:External searches]] -- a template special use case example
*[[Help:Variables]] -- fancy stuff you may find in some templates
*{{mediawiki|meta:Help:Embed page}} -- embedding pages from {{mediawiki|namespace|namespaces}} other than &lt;code&gt;Template:&lt;/code&gt;.

[[Category:Help|{{PAGENAME}}]]
[[Category:Template]]
{{Languages|Help:Templates}}</text>
    <sha1>5ce6580a0f1cd67c9143d47f1bd26a91b606f0c3</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Tables</title>
  <ns>12</ns>
  <id>18</id>
  <revision>
    <id>93</id>
    <parentid>92</parentid>
    <timestamp>2008-07-29T18:30:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10411" xml:space="preserve">{{PD Help Page}}

Tables may be authored in wiki pages using either HTML table elements directly, or using wikicode formatting to define the table. HTML table elements and their use are well described on various web pages and will not be discussed here. The benefit of wikicode is that the table is constructed of character symbols which tend to make it easier to perceive the table structure in the article editing view compared to HTML table elements.

A good general rule of thumb is to avoid using a table unless you need to. Table markup often complicates page editing.

== Wiki table markup summary ==

{|cellpadding="5" cellspacing="0" border="1" width="600"
|&lt;nowiki&gt;{|&lt;/nowiki&gt; || start '''table'''
|-
|&lt;nowiki&gt;|+&lt;/nowiki&gt; || table '''caption,''' ''optional;'' only one per table and between table start and first row
|-
|&lt;nowiki&gt;|-&lt;/nowiki&gt; || '''table row,''' ''optional on first row'' -- wiki engine assumes the first row
|-
|&lt;nowiki&gt;!&lt;/nowiki&gt;  || '''table header''' cell, ''optional.'' Consecutive table headers may be added on same line separated by double marks (!!) or start on new lines, each with its own single mark (!).
|- 
|&lt;nowiki&gt;|&lt;/nowiki&gt;  || '''table data''' cell, ''required!'' Consecutive table data cells may be added on same line separated by double marks (&lt;nowiki&gt;||&lt;/nowiki&gt;) or start on new lines, each with its own single mark (&lt;nowiki&gt;|&lt;/nowiki&gt;).
|-
|&lt;nowiki&gt;|}&lt;/nowiki&gt; || end '''table'''
|}
*The above marks must '''start on a new line''' except the double || and !! for optionally adding consecutive cells to a line.
*'''XHTML attributes.''' Each mark, except table end, optionally accepts one or more XHTML attributes. Attributes must be on the same line as the mark. Separate attributes from each other with a single space. 
**Cells and caption (&lt;nowiki&gt;| or ||, ! or !!, and |+&lt;/nowiki&gt;) hold content. So separate any attributes from content with a single pipe (|). Cell content may follow on same line or on following lines.
**Table and row marks (&lt;nowiki&gt;{| and |-&lt;/nowiki&gt;) do not directly hold content. Do ''not'' add pipe (|) after their optional attributes. If you erroneously add a pipe after attributes for the table mark or row mark the parser will delete it ''and'' your final attribute if it was touching the erroneous pipe!
*'''Content''' may (a) follow its cell mark on the same line after any optional XHTML attributes or (b) on lines below the cell mark. Content that uses wiki markup that itself needs to start on a new line, such as lists, headers, or nested tables, must of course be on its own new line.

==Simple table==

===Plain===
The following table lacks borders and good spacing but shows the simplest wiki markup table structure
{| width="100%"
|width="50%"|
{|
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{|
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

===Alternative===
For more table-ish looking wiki markup cells can be listed on one line separated by ||. This does not scale well for longer cell content such as paragraphs. It works well for short bits of content however, such as our example table.

Extra spaces within cells in the wiki markup can be added, as I have done in the wiki markup below, to make the wiki markup itself look better but they do not affect the actual table rendering.

HTML attributes can be added to tables on this page but have been left out of the following example for simplicity.
{| width="100%"
|width="50%"|
{|
|  Orange    ||   Apple   ||   more
|-
|   Bread    ||   Pie     ||   more
|-
|   Butter   || Ice cream ||  and more
|}
|width="50%"|
&lt;pre&gt;
{|
|  Orange    ||   Apple   ||   more
|-
|   Bread    ||   Pie     ||   more
|-
|   Butter   || Ice cream ||  and more
|}
&lt;/pre&gt;
|}

===With HTML attributes===
You can add HTML attributes to make your table look better
====border="1"====
{| width="100%"
|width="50%"|
{| border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

====align="center" border="1"====
{| width="100%"
|width="50%"|
{| align="center" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| align="center" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

====Attributes on cells ====
You can put attributes on individual '''cells.''' Numbers for example may look better aligned right
{| width="100%"
|width="50%"|
{| border="1"
|Orange
|Apple
|align="right"|12,333.00
|-
|Bread
|Pie
|align="right"|500.00
|-
|Butter
|Ice cream
|align="right"|1.00
|}
|width="50%"|
&lt;pre&gt;
{| border="1"
|Orange
|Apple
|align="right"|12,333.00
|-
|Bread
|Pie
|align="right"|500.00
|-
|Butter
|Ice cream
|align="right"|1.00
|}
&lt;/pre&gt;
|}

====Attributes on rows====
You can put attributes on individual '''rows,''' too.
{| width="100%"
|width="50%"|
{| border="1"
|Orange
|Apple
|align="right"|12,333.00
|-
|Bread
|Pie
|align="right"|500.00
|- style="font-style:italic;color:green;"
|Butter
|Ice cream
|align="right"|1.00
|}
|width="50%"|
&lt;pre&gt;
{| border="1"
|Orange
|Apple
|align="right"|12,333.00
|-
|Bread
|Pie
|align="right"|500.00
|- style="font-style:italic;color:green;"
|Butter
|Ice cream
|align="right"|1.00
|}
&lt;/pre&gt;
|}

====cellspacing="0" border="1"====
{| width="100%"
|width="50%"|
{| cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

====cellpadding="20" cellspacing="0" border="1"====
{| width="100%"
|width="50%"|
{| cellpadding="20" cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| cellpadding="20" cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

''Note: This cellpadding example is not currently working properly on mediawiki.org   It is supposed to look like [http://test.wikipedia.org/wiki/Table_test this]''

===With HTML attributes and CSS styles===
CSS style attributes can be added with or without other HTML attributes
====style="color:green;background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"====
{| width="100%"
|width="50%"|
{| style="color:green;background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| style="color:green;background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

==Table with TH headings==

TH (HTML table headings) can be created by using ! instead of |. Headings usually show up bold and centered by default.

===Top headings===
====Each column====
{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
!Yummy
!Yummier
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
!Yummy
!Yummier
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

====Colspan="2"====
{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
!colspan="2"|Yummies
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
! colspan="2"|Yummies
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

===Side headings===
====Default====
{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
!Fruit
|Orange
|Apple
|-
!Dish
|Bread
|Pie
|-
!Complement
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
!Fruit
|Orange
|Apple
|-
!Dish
|Bread
|Pie
|-
!Complement
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

====Right justify====
Right justified side headings can be done as follows
{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
!align="right" |Fruit
|Orange
|Apple
|-
!align="right" |Dish
|Bread
|Pie
|-
!align="right" |Complement
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
!align="right" |Fruit
|Orange
|Apple
|-
!align="right" |Dish
|Bread
|Pie
|-
!align="right" |Complement
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

==Caption==
A '''table caption''' can be added to the top of any table as follows
{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
|+Food complements
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
|+Food complements
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

'''Attributes''' can be added to the caption as follows

{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
|+align="bottom" style="color:#e76700;"|''Food complements''
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="1" cellpadding="20" cellspacing="0"
|+align="bottom" style="color:#e76700;"|''Food complements''
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

==Table with H1, H2, H3 etc. headings==

HTML H1, H2, H3, H4 etc. headings can be created the standard wiki markup way with ==equal== signs and '''must be on a line all by themselves''' to work.

'''Preview the whole table.''' If you click on an edit tab for a heading ''within'' a table, edit, and preview, the parent table will display erroneously broken because part of it will be missing.

Keep the heading hierarchy consistent with the rest of the page so that the table of contents at page top works correctly.

{| width="100%"
|width="50%"|
{| border="1" cellpadding="20" cellspacing="0"
|colspan="2"|
===Yummiest===
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
|width="50%"|
&lt;pre&gt;
{| border="3"  cellpadding="20" cellspacing="0"
|colspan="2"|
===Yummiest===
|-
|Orange
|Apple
|-
|Bread
|Pie
|-
|Butter
|Ice cream 
|}
&lt;/pre&gt;
|}

==Caveat==
===Negative numbers===
Negative value minus sign can break your table (it may display missing some values) if you start a cell on a new line with a negative number or a parameter that evaluates to a negative number (|-6) because that is the wiki markup for table row, not table cell. To avoid this, insert a space before the value (| -6) or use in-line cell markup (||-6).

{{Languages|Help:Tables}}
[[Category:Help|Tables]]
[[Category:Tables]]</text>
    <sha1>01828bc437c9dcaccd755715b5abef56d01cea23</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Variables</title>
  <ns>12</ns>
  <id>19</id>
  <revision>
    <id>95</id>
    <parentid>94</parentid>
    <timestamp>2008-07-29T18:30:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">#REDIRECT [[Help:Magic words]]</text>
    <sha1>c8b7e8094709335f482db7202d3de936277fc007</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Magic words</title>
  <ns>12</ns>
  <id>21</id>
  <revision>
    <id>98</id>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15862" xml:space="preserve">{{PD Help Page}}

'''Magic words''' are strings of text that MediaWiki associates with a return value or function, such as time, site details, or page names. This page is about usage of standard magic words; for a technical reference, see {{mediawiki|Manual:Magic words}}.

==General notes==
* '''Inheritance:''' page-dependent magic words will affect or return data about the current page, regardless of whether it is in the page code or a transcluded template.

==Behaviour switches==
A behaviour switch controls the layout of the page. They are written as a magic word wrapped with double underscores.

{| {{prettytable}}
|-
!{{Hl2}}| Word
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
|{{Hl3}} colspan="3"| '''Table of contents'''
|-
| &lt;nowiki&gt;__NOTOC__&lt;/nowiki&gt;
| Hides the table of contents (TOC).
|
|-
|&lt;nowiki&gt;__FORCETOC__&lt;/nowiki&gt;
| Forces the table of content to appear at its normal position (above the first header).
|
|-
| &lt;nowiki&gt;__TOC__&lt;/nowiki&gt;
| Places a table of contents at the word's current position (overriding &lt;nowiki&gt;__NOTOC__&lt;/nowiki&gt;). If this is used multiple times, the table of contents will appear at the first word's position.
|
|-
|{{Hl3}} colspan="3"| '''Editing'''
|-
| &lt;nowiki&gt;__NOEDITSECTION__&lt;/nowiki&gt;
| Hides the section edit links beside headings.
|
|-
| &lt;nowiki&gt;__NEWSECTIONLINK__&lt;/nowiki&gt;
| Adds a link (([[MediaWiki:Addsection|"+" by default]]) beside the "edit" tab for adding a new section on a non-talk page (see {{mediawiki|m:Help:Section#Adding a section at the end}}).
| 1.7+
|-
|{{Hl3}} colspan="3"| '''Categories'''
|-
| &lt;nowiki&gt;__NOGALLERY__&lt;/nowiki&gt;
| Used on a category page, replaces thumbnails in the category view with normal links.
| 1.7+
|-
| &lt;nowiki&gt;__HIDDENCAT__&lt;/nowiki&gt;
| Used on a category page, hides the category from the lists of categories in its members and parent categories (there is an option in the [[Help:Preferences|user preferences]] to show them).
| 1.13+
|-
|{{Hl3}} colspan="3"| '''Language conversion'''
|-
| &lt;nowiki&gt;__NOCONTENTCONVERT__&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;__NOCC__&lt;/nowiki&gt;
| On wikis with language variants, don't perform any content language conversion (character and phase) in article display; for example, only show Chinese (zh) instead of variants like zh_cn, zh_tw, zh_sg, or zh_hk.
|
|-
| &lt;nowiki&gt;__NOTITLECONVERT__&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;__NOTC__&lt;/nowiki&gt;
| On wikis with language variants, don't perform language conversion on the title (all other content is converted).
|
|-
|{{Hl3}} colspan="3"| '''Other'''
|-
| &lt;nowiki&gt;__END__&lt;/nowiki&gt;
| Explicitly marks the end of the article, to prevent MediaWiki from removing trailing whitespace. Removed in {{mediawiki|rev:19213|19213}}.
|
|-
| &lt;nowiki&gt;__START__&lt;/nowiki&gt;
| No effect.
|
|}

==Variables and parser functions==
Variables return information about the current page, wiki, or date. Their syntax is similar to [[Help:Templates|templates]], but capitalized to help avoid conflicts. If a template has the same name and case as a variable, the variable will be used. Usage of the template can be forced by adding the "msg:" modifier (for example, "&lt;code&gt;&lt;nowiki&gt;{{msg:CURRENTYEAR}}&lt;/nowiki&gt;&lt;/code&gt;"). In some cases, adding parameters will force the parser to treat a variable as a template; for example, &lt;code&gt;&lt;nowiki&gt;{{CURRENTDAYNAME|x}}&lt;/nowiki&gt;&lt;/code&gt; tries to transclude "Template:CURRENTDAYNAME".

Parser functions are very similar to variables, but operate on user input instead of the current page. The first parameter is delimited by a colon (:) instead of a pipe (|). (This page does not document custom parser functions added by the {{mediawiki|Extension:ParserFunctions|ParserFunctions extension}}.)

===Date &amp; time===
The following variables return the current date and time according to the user's timezone [[Special:Preferences|preferences]], defaulting to the UTC timezone.

Due to MediaWiki and browser caching, these variables frequently show when the page was ''cached'' rather than the current time.

{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
|{{Hl3}} colspan="4"| '''Year'''
|-
| &lt;nowiki&gt;{{CURRENTYEAR}}&lt;/nowiki&gt;
| {{CURRENTYEAR}}
| Year
|
|-
|{{Hl3}} colspan="4"| '''Month'''
|-
| &lt;nowiki&gt;{{CURRENTMONTH}}&lt;/nowiki&gt; 
| {{CURRENTMONTH}}
| Month (zero-padded number)
|
|-
| &lt;nowiki&gt;{{CURRENTMONTHNAME}}&lt;/nowiki&gt;
| {{CURRENTMONTHNAME}}
| Month (name)
|
|-
| &lt;nowiki&gt;{{CURRENTMONTHNAMEGEN}}&lt;/nowiki&gt;
| {{CURRENTMONTHNAMEGEN}}
| Month ([http://en.wikipedia.org/wiki/genitive genitive form])
|
|-
| &lt;nowiki&gt;{{CURRENTMONTHABBREV}}&lt;/nowiki&gt;
| {{CURRENTMONTHABBREV}}
| Month (abbreviation)
| 1.5+
|-
|{{Hl3}} colspan="4"| '''Day'''
|-
| &lt;nowiki&gt;{{CURRENTDAY}}&lt;/nowiki&gt;
| {{CURRENTDAY}}
| Day of the month (unpadded number)
|
|-
| &lt;nowiki&gt;{{CURRENTDAY2}}&lt;/nowiki&gt;
| {{CURRENTDAY2}}
| Day of the month (zero-padded number)
| 1.6+
|-
| &lt;nowiki&gt;{{CURRENTDOW}}&lt;/nowiki&gt;
| {{CURRENTDOW}}
| Day of the week (unpadded number)
|
|-
| &lt;nowiki&gt;{{CURRENTDAYNAME}}&lt;/nowiki&gt;
| {{CURRENTDAYNAME}}
| Day of the week (name)
|
|-
|{{Hl3}} colspan="4"| '''Time'''
|-
| &lt;nowiki&gt;{{CURRENTTIME}}&lt;/nowiki&gt;
| {{CURRENTTIME}}
| Time (24-hour HH:mm format)
|
|-
| &lt;nowiki&gt;{{CURRENTHOUR}}&lt;/nowiki&gt;
| {{CURRENTHOUR}}
| Hour (24-hour zero-padded number)
|
|-
|{{Hl3}} colspan="4"| '''Other'''
|-
| &lt;nowiki&gt;{{CURRENTWEEK}}&lt;/nowiki&gt;
| {{CURRENTWEEK}}
| Week (number)
|
|-
| &lt;nowiki&gt;{{CURRENTTIMESTAMP}}&lt;/nowiki&gt;
| {{CURRENTTIMESTAMP}}
| [[wikipedia:ISO 8601|ISO 8601]] time stamp
| 1.7+
|}

The following variables do the same as the above, but using the site's local timezone instead of user preferences and UTC:
* &lt;nowiki&gt;{{LOCALYEAR}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALMONTH}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALMONTHNAME}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALMONTHNAMEGEN}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALMONTHABBREV}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALDAY}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALDAY2}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALDOW}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALDAYNAME}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALTIME}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALHOUR}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALWEEK}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{LOCALTIMESTAMP}}&lt;/nowiki&gt;

===Technical metadata===
Revision variables return data about the '''latest edit to the current page''', even if viewing an older version of the page.
{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
|{{Hl3}} colspan="4"| '''Site'''
|-
| &lt;nowiki&gt;{{SITENAME}}&lt;/nowiki&gt;
| {{SITENAME}}
| The wiki's site name ({{mediawiki|Manual:$wgSitename|$wgSitename}}).
|
|-
| &lt;nowiki&gt;{{CURRENTVERSION}}&lt;/nowiki&gt;
| {{CURRENTVERSION}}
| The wiki's MediaWiki version.
| 1.7+
|-
| &lt;nowiki&gt;{{CONTENTLANGUAGE}}&lt;/nowiki&gt;
| {{CONTENTLANGUAGE}}
| The wiki's default interface language ({{mediawiki|Manual:$wgLanguageCode|$wgLanguageCode}})
|
|-
|{{Hl3}} colspan="4"| '''Latest revision to current page'''
|-
| &lt;nowiki&gt;{{REVISIONID}}&lt;/nowiki&gt;
| {{REVISIONID}}
| Unique ID
|
|-
| &lt;nowiki&gt;{{REVISIONDAY}}&lt;/nowiki&gt;
| {{REVISIONDAY}}
| Day edit was made (unpadded number)
|
|-
| &lt;nowiki&gt;{{REVISIONDAY2}}&lt;/nowiki&gt;
| {{REVISIONDAY2}}
| Day edit was made (zero-padded number)
|
|-
| &lt;nowiki&gt;{{REVISIONMONTH}}&lt;/nowiki&gt;
| {{REVISIONMONTH}}
| Month edit was made (unpadded number)
|
|-
| &lt;nowiki&gt;{{REVISIONYEAR}}&lt;/nowiki&gt;
| {{REVISIONYEAR}}
| Year edit was made
|
|-
| &lt;nowiki&gt;{{REVISIONTIMESTAMP}}&lt;/nowiki&gt;
| {{REVISIONTIMESTAMP}}
| Timestamp as of time of edit
|
|}

===Statistics===
Numbers returned by these variables contain number separators, but can return raw numbers with the ":R" flag (for example, &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFPAGES}}&lt;/nowiki&gt;&lt;/code&gt; = {{NUMBEROFPAGES}} and &lt;code&gt;&lt;nowiki&gt;{{NUMBEROFPAGES:R}}&lt;/nowiki&gt;&lt;/code&gt; = {{NUMBEROFPAGES:R}}). Use "|R" for magic words that require a parameter like PAGESINCATEGORY (for example &lt;code&gt;&lt;nowiki&gt;{{PAGESINCATEGORY:Help}}&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;{{PAGESINCATEGORY:Help|R}}&lt;/nowiki&gt;&lt;/code&gt;).
{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
|{{Hl3}} colspan="4"| '''Entire wiki'''
|-
| &lt;nowiki&gt;{{NUMBEROFPAGES}}&lt;/nowiki&gt;
| {{NUMBEROFPAGES}}
| Number of wiki pages.
| 1.7+
|-
| &lt;nowiki&gt;{{NUMBEROFARTICLES}}&lt;/nowiki&gt;
| {{NUMBEROFARTICLES}}
| Number of pages in main namespace.
|
|-
| &lt;nowiki&gt;{{NUMBEROFFILES}}&lt;/nowiki&gt;
| {{NUMBEROFFILES}}
| Number of uploaded files.
| 1.5+
|-
| &lt;nowiki&gt;{{NUMBEROFEDITS}}&lt;/nowiki&gt;
| {{NUMBEROFEDITS}}
| Number of page edits.
| {{mediawiki|rev:21319|1.10+}}
|-
| &lt;nowiki&gt;{{NUMBEROFUSERS}}&lt;/nowiki&gt;
| {{NUMBEROFUSERS}}
| Number of registered users.
| 1.7+
|-
| &lt;nowiki&gt;{{NUMBEROFADMINS}}&lt;/nowiki&gt;
| {{NUMBEROFADMINS}}
| Number of users in in the ''sysop'' {{mediawiki|Manual:User rights|group}}.
| 1.7+
|-
|{{Hl3}} colspan="4"| '''Per namespace'''
|-
| &lt;nowiki&gt;{{PAGESINNS:2}}&lt;/nowiki&gt;
| {{PAGESINNS:2}}
| Number of pages in the given [[Help:Namespaces|namespace]] (replace 2 with the relevant namespace ID). Disabled by default, enable with {{mediawiki|Manual:$wgAllowSlowParserFunctions|$wgAllowSlowParserFunctions}}.
| 1.7+
|-
| &lt;nowiki&gt;{{PAGESINNAMESPACE:2}}&lt;/nowiki&gt;
| {{PAGESINNAMESPACE:2}}
| Alias for &lt;code&gt;&lt;nowiki&gt;{{PAGESINNS}}&lt;/nowiki&gt;&lt;/code&gt;.
| 1.7+
|-
|{{Hl3}} colspan="4"| '''Other'''
|-
| &lt;nowiki&gt;{{PAGESINCATEGORY:Help}}&lt;/nowiki&gt;
| {{PAGESINCATEGORY:Help}}
| Number of pages in the given [[Help:Categories|category]] (replace "Help" with the relevant category name).
| 1.13+
|-
| &lt;nowiki&gt;{{PAGESINCAT:Help}}&lt;/nowiki&gt;
| {{PAGESINCAT:Help}}
| Alias for &lt;code&gt;&lt;nowiki&gt;{{PAGESINCATEGORY}}&lt;/nowiki&gt;&lt;/code&gt;.
| 1.13+
|-
| &lt;nowiki&gt;{{PAGESIZE:Help:Magic_words}}&lt;/nowiki&gt;
| {{PAGESIZE:Help:Magic_words}}
| Returns the byte size of the specified page.
| {{mediawiki|rev:33551|1.13+}}
|}

===URL data===
====URLs====
{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
| &lt;nowiki&gt;{{SERVER}}&lt;/nowiki&gt;
| {{SERVER}}
| domain URL ({{mediawiki|Manual:$wgServer|$wgServer}})
|
|-
| &lt;nowiki&gt;{{SERVERNAME}}&lt;/nowiki&gt;
| {{SERVERNAME}}
| domain name ({{mediawiki|Manual:$wgServerName|$wgServerName}})
|
|-
| &lt;nowiki&gt;{{SCRIPTPATH}}&lt;/nowiki&gt;
| {{SCRIPTPATH}}
| relative script path ({{mediawiki|Manual:$wgScriptPath|$wgScriptPath}})
|
|-
| &lt;nowiki&gt;{{localurl:&lt;/nowiki&gt;''page name''&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;{{localurl:page name|&lt;/nowiki&gt;''query string''&lt;nowiki&gt;}}&lt;/nowiki&gt;
| {{localurl:page name}}&lt;br /&gt;{{localurl:page name|query string}}
| relative path to title
|
|-
| &lt;nowiki&gt;{{fullurl:&lt;/nowiki&gt;''page name''&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;{{fullurl:page name|&lt;/nowiki&gt;''query_string''&lt;nowiki&gt;}}&lt;/nowiki&gt;
| {{fullurl:page name}}&lt;br /&gt;{{fullurl:page name|query_string}}
| absolute path to title
| 1.5+
|-
| &lt;nowiki&gt;{{filepath:Wiki.png}}&lt;/nowiki&gt;
| {{filepath:Wiki.png}}
| The absolute URL to a media file.
| {{mediawiki|rev:25854|1.12+}}
|-
| &lt;nowiki&gt;{{urlencode:x y z}}&lt;/nowiki&gt;
| &lt;code&gt;{{urlencode:xyz}}&lt;/code&gt;
| The input encoded for use in URLs.
| {{mediawiki|rev:14273|1.7+}}
|-
| &lt;nowiki&gt;{{anchorencode:x y z}}&lt;/nowiki&gt;
| &lt;code&gt;{{anchorencode:x y z}}&lt;/code&gt;
| The input encoded for use in URL section anchors (after the '#' symbol in a URL).
| {{mediawiki|rev:16279|1.8+}}
|}

====Page names====
{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
| &lt;nowiki&gt;{{FULLPAGENAME}}&lt;/nowiki&gt;
| {{FULLPAGENAME}}
| Namespace and page title.
|
|-
| &lt;nowiki&gt;{{PAGENAME}}&lt;/nowiki&gt;
| {{PAGENAME}}
| Page title.
|
|-
| &lt;nowiki&gt;{{BASEPAGENAME}}&lt;/nowiki&gt;
| {{BASEPAGENAME}}
| Page title excluding the current [[Help:Subpages|subpage]] and namespace ("Title" on "Title/foo").
| 1.7+
|-
| &lt;nowiki&gt;{{SUBPAGENAME}}&lt;/nowiki&gt;
| {{SUBPAGENAME}}
| The [[Help:Subpages|subpage]] title ("foo" on "Title/foo").
| 1.6+
|-
| &lt;nowiki&gt;{{SUBJECTPAGENAME}}&lt;/nowiki&gt;
| {{SUBJECTPAGENAME}}
| The namespace and title of the associated content page.
| 1.7+
|-
| &lt;nowiki&gt;{{TALKPAGENAME}}&lt;/nowiki&gt;
| {{TALKPAGENAME}}
| The namespace and title of the associated talk page.
| 1.7+
|}

The following are URL-encoded equivalents:
* &lt;nowiki&gt;{{FULLPAGENAMEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{PAGENAMEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{BASEPAGENAMEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{SUBPAGENAMEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{SUBJECTPAGENAMEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{TALKPAGENAMEE}}&lt;/nowiki&gt;

====Namespaces====
{| {{prettytable}}
|-
!{{Hl2}}| Variable
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Versions
|-
| &lt;nowiki&gt;{{NAMESPACE}}&lt;/nowiki&gt;
| {{NAMESPACE}}
| Namespace (name)
|-
| &lt;nowiki&gt;{{SUBJECTSPACE}}&lt;/nowiki&gt;
| {{SUBJECTSPACE}}
| Name of the associated content namespace
|-
| &lt;nowiki&gt;{{TALKSPACE}}&lt;/nowiki&gt;
| {{TALKSPACE}}
| Name of the associated talk namespace
|}

The following are URL-encoded equivalents:
* &lt;nowiki&gt;{{NAMESPACEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{SUBJECTSPACEE}}&lt;/nowiki&gt;
* &lt;nowiki&gt;{{TALKSPACEE}}&lt;/nowiki&gt;

&lt;code&gt;&lt;nowiki&gt;{{ns:}}&lt;/nowiki&gt;&lt;/code&gt; returns the localized namespace name for that number constant. The default values are:
{| {{prettytable}}
|-
!{{Hl2}}| Usage
!{{Hl2}}| Output
|-
| &lt;nowiki&gt;{{ns:-2}} or {{ns:Media}}&lt;/nowiki&gt;
| {{ns:-2}}
|-
| &lt;nowiki&gt;{{ns:-1}} or {{ns:Special}}&lt;/nowiki&gt;
| {{ns:-1}}
|-
| &lt;nowiki&gt;{{ns:0}}&lt;/nowiki&gt;
| {{ns:0}}
|-
| &lt;nowiki&gt;{{ns:1}} or {{ns:Talk}}&lt;/nowiki&gt;
| {{ns:1}}
|-
| &lt;nowiki&gt;{{ns:2}} or {{ns:User}}&lt;/nowiki&gt;
| {{ns:2}}
|-
| &lt;nowiki&gt;{{ns:3}} or {{ns:User_talk}}&lt;/nowiki&gt;
| {{ns:3}}
|-
| &lt;nowiki&gt;{{ns:4}} or {{ns:Project}}&lt;/nowiki&gt;
| {{ns:4}}
|-
| &lt;nowiki&gt;{{ns:5}} or {{ns:Project_talk}}&lt;/nowiki&gt;
| {{ns:5}}
|-
| &lt;nowiki&gt;{{ns:6}} or {{ns:Image}}&lt;/nowiki&gt;
| {{ns:6}}
|-
| &lt;nowiki&gt;{{ns:7}} or {{ns:Image_talk}}&lt;/nowiki&gt;
| {{ns:7}}
|-
| &lt;nowiki&gt;{{ns:8}} or {{ns:MediaWiki}}&lt;/nowiki&gt;
| {{ns:8}}
|-
| &lt;nowiki&gt;{{ns:9}} or {{ns:MediaWiki_talk}}&lt;/nowiki&gt;
| {{ns:9}}
|-
| &lt;nowiki&gt;{{ns:10}} or {{ns:Template}}&lt;/nowiki&gt;
| {{ns:10}}
|-
| &lt;nowiki&gt;{{ns:11}} or {{ns:Template_talk}}&lt;/nowiki&gt;
| {{ns:11}}
|-
| &lt;nowiki&gt;{{ns:12}} or {{ns:Help}}&lt;/nowiki&gt;
| {{ns:12}}
|-
| &lt;nowiki&gt;{{ns:13}} or {{ns:Help_talk}}&lt;/nowiki&gt;
| {{ns:13}}
|-
| &lt;nowiki&gt;{{ns:14}} or {{ns:Category}}&lt;/nowiki&gt;
| {{ns:14}}
|-
| &lt;nowiki&gt;{{ns:15}} or {{ns:Category_talk}}&lt;/nowiki&gt;
| {{ns:15}}
|}

===Formatting===
{| {{prettytable}}
!{{Hl2}}| Usage
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Version
|-
|-
| &lt;nowiki&gt;{{lc:XYZ}}&lt;/nowiki&gt;
| {{lc:XYZ}}
| The lowercase input.
| 1.5+
|-
| &lt;nowiki&gt;{{lcfirst:XYZ}}&lt;/nowiki&gt;
| {{lcfirst:XYZ}}
| The input with the first character lowercase.
| 1.5+
|-
| &lt;nowiki&gt;{{uc:xyz}}&lt;/nowiki&gt;
| {{uc:xyz}}
| The uppercase input.
| 1.5+
|-
| &lt;nowiki&gt;{{ucfirst:xyz}}&lt;/nowiki&gt;
| {{ucfirst:xyz}}
| The input with the first character uppercase.
| 1.5+
|-
| &lt;nowiki&gt;{{formatnum:-987654321.654321}}&lt;/nowiki&gt;
| {{formatnum:-987654321.654321}}
| The input with decimal and decimal group separators, and localized digit script, according to the wiki's default locale.
| 1.7+
|-
| &lt;nowiki&gt;{{padleft:xyz|5|_}}&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;{{padleft:xyz|5}}&lt;/nowiki&gt;
| {{padleft:xyz|5|_}}&lt;br /&gt;{{padleft:xyz|5}}
| The input (first parameter) padded on the left side to the specified width (second parameter) using the specified character (third parameter). If a padding character isn't specified, '0' is used by default.&lt;br /&gt;'''bug:''' multibyte characters are interpreted as two characters, which can skew width. These also cannot be used as padding characters.
| 1.8+
|-
| &lt;nowiki&gt;{{padright:xyz|5|_}}&lt;/nowiki&gt;&lt;br /&gt;&lt;nowiki&gt;{{padright:xyz|5}}&lt;/nowiki&gt;
| {{padright:xyz|5|_}}&lt;br /&gt;{{padright:xyz|5}}
| Identical to padleft, but adds padding characters to the right side.
|}

===Miscellaneous===
{| {{prettytable}}
!{{Hl2}}| Usage
!{{Hl2}}| Output
!{{Hl2}}| Description
!{{Hl2}}| Version
|-
| &lt;nowiki&gt;{{#language:eo}}&lt;/nowiki&gt; 
| {{#language:eo}}
| The native name for the given language code.
| 1.7+
|-
| &lt;nowiki&gt;{{#special:userlogin}}&lt;/nowiki&gt;
| {{#special:userlogin}}
| The localized name for the given canonical Special: page.
| {{mediawiki|rev:17321|1.9+}}
|}

{{Languages|Help:Variables}}

[[Category:Help|{{PAGENAME}}]]
[[Category:Time|{{PAGENAME}}]]
[[Category:Magic words|{{PAGENAME}}]]</text>
    <sha1>11873379f36a8ff8ec6035db56e4f60251dc0bc1</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Moving a page</title>
  <ns>12</ns>
  <id>22</id>
  <revision>
    <id>101</id>
    <parentid>100</parentid>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2423" xml:space="preserve">{{PD Help Page}}

'''Moving (renaming) a page''' means giving it another name. This is done by using "{{int:move}}" tab at the top. Then simply enter the new name and click 'Move Page'. Normally you would want to leave "Move associated talk page" option ticked.  

If you move page "A" to a new title "B", this operation will do the following:
* Creates the new page "B", with contents from page "A"
* Replaces the contents of page "A" with redirect to "B"
* Moves all the editing history from page "A" so that it appears under "B"'s history tab.
&lt;!--I think the above describes just the opposite to what actually happens in the database, I'm going to replace it with correct description: page is not actually moved in [[Page table]], it's simply given a new title--&gt;

The third point is important. By using the 'Move' feature, you also '''move the editing history''', which is desireable in most situations. The editing history allows people to see how the contents of the page were built up, and who contributed what. If you move contents around by copying and pasting (not using the move feature), you do not achieve this.

Because the move operation '''leaves behind a redirect''', it should not result in any broken links, however you might want to hunt down the pages which link in to the redirect, and change their text to link directly to the new title. The 'What links here' toolbox feature (bottom left) is useful when doing this.

== Proposing a move ==
Deciding on a page title can be a difficult aspect of wiki organization, and one which can often provoke debates. If the move you have in mind is one which might cause upset or could be considered controversial, you should propose the move first. Do this by leaving a note to give your reasons on the [[Help:Talk pages|talk page]]. You might also establish a system for labelling the page itself, with a move proposal template, to make everybody aware of your intentions.

== Undo a move ==
As with all wiki editing, a move operation can be reversed (by any user).  To reverse a move operation, simply move the page back, e.g. move page "B" back to "A".

The page title "B" will still be left behind, as a redirect from "B" to "A". Any user can remove the redirect and propose that the page be deleted. However the final deletion will require sysop privileges (see [[Help:Deleting a page]]).

{{Languages|Help:Moving a page}}

[[Category:Help|Moving a page]]</text>
    <sha1>1c453108b5ed4bca932a54fff6a821536b5b05aa</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Redirects</title>
  <ns>12</ns>
  <id>23</id>
  <revision>
    <id>102</id>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3180" xml:space="preserve">{{PD Help Page}}

Redirects are used to forward users from one page name to another. They can be useful if a particular article is referred to by multiple names, or has alternative punctuation, capitalization or spellings.

==Creating a redirect==
To create a redirect, you must start a new page with the name you want to direct from. Do this by typing the desired name into the search box, or straight into the URL (methods described on [[Help:Starting a new page]])

For the text of the new page, enter the following:
 &lt;nowiki&gt;#REDIRECT [[&lt;/nowiki&gt;''pagename''&lt;nowiki&gt;]]&lt;/nowiki&gt;
where ''pagename'' is the name of the page you want to redirect users to.

You can use the 'preview' button, to check that you have entered the correct page name (Generally you will be redirecting to an existing page name, so the link should be blue, not red)

==Viewing a redirect==
After creating a redirect, you can no longer get to that page name. The browser is always redirected! However near the top of the page, a link is provided. Click this to get back to the redirected page name, and "view" the redirect.

By doing this, you can do all the things that any wiki page allows. You can go to the associated discussion page to discuss the redirect. You can view the history of the page before the redirect was put in place. You edit the page if the redirect is wrong, and you can revert to an older version to remove the redirect.

==Deleting a redirect==
There's generally no need to delete redirects. They do not occupy a significant amount of database space, and they do not show up in wiki search results. If a page name is vaguely meaningful there's no harm (and some benefit) in having it as a redirect to the most relevant existing page in your wiki. However...

If you ''do'' need to delete a redirect, e.g. if the page name of the redirect is offensive, or you wish to discourage people from referring to concept by that name, then you simply go to the redirect page, and follow the same procedure for deleting a page. See: [[Help:Deleting a page]]

==Double redirects ==
A double redirect (a page redirecting to a page which is itself a redirect) will not work. The redirecting will not follow through to the end of the chain. Instead people will just be presented with the relevant link (a view of the redirect page). This is a deliberate restriction, partly to prevent infinite loops, and partly to keep things simple. It avoids people building up an unpleasantly complicated tree of redirects!

However this does mean that you should look out for double redirects and eliminate them, by changing them to be 1-step redirects instead. You are most likely to need to do this after a significant [[Help:Moving a page|page move]]. Use the 'what links here' toolbox link to find double redirects to a particular page, or use [[Special:DoubleRedirects]] to find them throughout the whole wiki.

== A redirect to a page in the category namespace ==
To prevent a page that redirects to a category from appearing in the category; precede the word Category with a colon like so : &lt;nowiki&gt;#REDIRECT [[:Category:Glossary]]&lt;/nowiki&gt;

{{Languages|Help:Redirects}} 

[[Category:Help|Redirects]]</text>
    <sha1>78a20019e831f4c3ac30a789eccaee4116e469f2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Deleting a page</title>
  <ns>12</ns>
  <id>24</id>
  <revision>
    <id>105</id>
    <parentid>104</parentid>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3196" xml:space="preserve">{{#ifexist: Template:PD Help Page/{{SUBPAGENAME}}|{{PD Help Page/{{SUBPAGENAME}}}}|{{PD Help Page}}}}


== When to delete a page : ==
Typically you would delete a page if the contents are entirely inappropriate, and do not match the purposes of the wiki. In other situations you might prefer a less extreme course of action, for example...

* The page should have a different title - So just "move" the page to a better title. See [[Help:Moving a page]]
* The contents should have been placed on a different page - So "merge" the contents into the existing page and then create a redirect. See [[Help:Redirects]]
* The contents are already on a different page - So wipe away all the duplicate content and leave behind a redirect. That way, this page title (which made more sense to somebody), will helpfully redirect to the correct location of the information. See [[Help:Redirects]]
* The page is out-of-date - So update it! If the page describes a current or future event, which has now passed, reword all of the sentences to be in the past tense, that way you have created a page which acts as a historical record. Alternatively label the information as out-of-date, with a warning notice.

So in fact a straightforward delete is generally only necessary if the ''title'' of the page is inappropriate. In other situations, a merge and redirect is more appropriate.

=== Proposing changes ===
Deciding on appropriate content/page titles can be a difficult aspect of wiki organization, and one which can often provoke debates. If the merge or deletion you have in mind, is one which might cause upset, you should propose the change first. Do this by leaving a note to give your reasons on the [[Help:Talk pages|talk page]]. You might also establish a system for labeling the page itself, with a delete/merge proposal template, to make everybody aware of your intentions

=== Unlinking a page ===
If a page is no longer of any value, then you won't have any links pointing to it right? Well you might be surprised. The 'What links here' toolbox feature (bottom left) will tell you which other wiki pages link in to the current page. Always use this feature to check before proceeding with deleting. These related pages will need to be edited, to reflect the change.

== Deletion itself ==
'''Normal users''' cannot permanently delete a wiki page. This is an entirely deliberate design feature, which is an important part of why wikis work. Every kind of editing operation can be reverted by any other user, and that includes resurrecting deleted content. Try not to let it wind you up too much. It doesn't cause significant wasted space, and with nothing but a 'delete' label the page is effectively deleted anyway.

'[[Help:Sysops and permissions|Sysop]]' users ''are'' able to delete a page semi-permanently. See [[Help:Sysop deleting and undeleting]]. Typically sysops might look for delete labels, and do a proper delete on these pages, after a period of time. If for some reason you need a page to be deleted more quickly than that, you will need to contact a sysop to request this.

==See also==
* [[Help:Sysops and permissions]]

{{Languages|Help:Deleting a page}}

{{Help/Category|Help}}</text>
    <sha1>cf0561c6c49b4b2bcd4a08b7f72a4f262b351202</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Protected pages</title>
  <ns>12</ns>
  <id>25</id>
  <revision>
    <id>106</id>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="610" xml:space="preserve">{{PD Help Page}}
A '''protected page''' is a page where normal users are prevented from editing at all. Only a user with [[Help:Sysops and permissions|sysop permissions]] can edit a protected page. Likewise only sysop users can protect a page in the first place, or unprotect the page to lift the restriction.

There are several reasons why a particular page might be protected. Typically a protected page is one which has been repeatedly targeted with vandalism, or where it is believed that vandalism would have a unusually severe impact.

For sysop information see [[Help:Protecting and unprotecting pages]]</text>
    <sha1>e8781c3c0db1c7d032f1755a96095008b5ae32ce</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Preferences</title>
  <ns>12</ns>
  <id>26</id>
  <revision>
    <id>109</id>
    <parentid>108</parentid>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6958" xml:space="preserve">{{PD Help Page}}

Clicking on the [[Special:preferences|my preferences]] link in the upper right while logged in allows you to change your preferences. You will be presented with the User profile section, as well as a bar of tabs across the top for changing other types of settings.

==User profile==
===User profile===
* ''Username'': Your user name. Only bureaucrats can change your username, and the wiki must also have the {{mediawiki|Extension:Renameuser|Renameuser extension}} installed.
* ''User ID'': A number assigned to your account when you created it (for example, if your number is 42 you are the 42nd user to sign up at this particular wiki). This number is used for internal purposes.
* ''Number of edits'': How many edits you have made. Not all wikis will have this.
* ''Real name'': If provided, this will be used for attribution (rather than using your username). Providing your real name is entirely optional. Some wikis do not have this option.
* ''E-mail'': Your email address, if you have supplied one. You can also change or remove your address here.
* ''Nickname'': When you sign your name (using &lt;code&gt;&lt;nowiki&gt;~~~~&lt;/nowiki&gt;&lt;/code&gt;), what you enter here will be used at the start instead of a simple link to your user page. By default, anything you enter here will be wrapped with &lt;code&gt;&lt;nowiki&gt;[[ ]]&lt;/nowiki&gt;&lt;/code&gt;; if you want to use special linking, enable ''Raw signatures (without automatic link)''.
* ''Language'': This controls what language the interface is displayed in.  MediaWiki's default interface includes localisations for all supported languages, but this is not necessarily the case with extensions or custom skins. Page text will '''not''' be translated, nor will templates (unless the templates integrate text localisation).

===Change password===
To change your password, enter your old password in the first box and your new password in the last two. If you want this site to remember your login, check ''Remember my login on this computer''. Note that this function requires you to have cookies enabled in your browser, and if your cookie is cleared or expires you will no longer be remembered.

===E-mail===
If you have supplied an email address, you will need to click the ''verify address'' button in order to use these functions. You will receive an email; simply open it and follow the link to enable the following functions.

* ''E-mail me when a page I'm watching is changed''
* ''E-mail me when my user talk page is changed''
* ''E-mail me also for minor edits of pages''
* ''Enable e-mail from other users''
* ''Send me copies of emails I send to other users''

===Languages===

From your preferences you can select what language you would like the interface to be in. Only the buttons like 'edit' and 'talk', in addition to a few pages in the sidebar, will be affected. The main text of the pages will not be changed by this for the vast majority of pages, although there are a few pages where it will, like some in the Wikimedia Meta Wiki.

==Skin==
Here you can choose the skin you want to use (use ''Preview'' if you want to see a skin before you choose it). By default, MediaWiki includes the following skins:
* Chick
* Classic
* Cologne Blue
* MonoBook (default)
* MySkin
* Nostalgia
* Simple
While you can choose whatever skin you like, bear in mind that some wikis will incorporate templates or layout elements that will not display as intended in some of these skins. Generally speaking, sticking with MonoBook (or whatever the wiki's default skin is) will ensure you see pages as intended.

==Math==
Here you can control how mathematical equations described using the &lt;code&gt;&lt;nowiki&gt;&lt;math&gt;&lt;/nowiki&gt;&lt;/code&gt; tag will be displayed. Mathematical formulae uploaded as images or written outside the math tag will not be affected by this setting.
* ''Always render PNG''
* ''HTML if very simple or else PNG''
* ''HTML if possible or else PNG''
* ''Leave it as TeX (for text browsers)''
* ''Recommended for modern browsers''
* ''MathML if possible (experimental)''

==Files==
Here you can determine how images will be displayed. Images displayed by direct pasting of a URL (if the wiki has it enabled) will not be affected by this setting.

* ''Limit images on image description pages to'': This setting lets you choose how big image previews will be on the Image: pages. If you know what your current screen resolution is you may like to set this to one or two sizes smaller than your own screen. If you have a slow connection (such as dial-up) you may want to limit them to 320×240.
* ''Thumbnail size'': Define how big you want thumbnails to appear. This setting will not affect thumbnails with dimensions determined by an editor, nor can it increase images beyond their original dimensions.

==Date and time==
The following is normally rendered depending on preferences:

&lt;pre&gt;
 [[2001-01-05]] (or [[2001]]-[[01-05]]) (with leading zeros)
 [[2001]] [[January 5]] ([[2001]] [[January 05]])
 [[January 5]], [[2001]] ([[January 05]], [[2001]])
 [[5 January]] [[2001]] ([[05 January]] [[2001]])
 [[January 5]] ([[January 05]])
 [[5 January]] ([[05 January]])
&lt;/pre&gt;

==Editing==
Settings to control editing pages, including the size of the edit box displayed and whether to watch pages that you have edited or created automatically.

==Recent changes==
* ''Days to show in recent changes'': Here you can specify how far back the [[Help:Tracking changes|recent changes]] pages will go. Note that the list will stop prematurely if the number of edits is exceeded (see below)
* ''Number of edits to show in recent changes'': Here you can specify how many edits should be displayed.
* ''Hide minor edits in recent changes'': This enables you to hide edits marked as minor (see [[Help:Editing pages]]). Since some users will rapidly make a lot of tiny tweaks to update templates or fix spelling errors you may find enabling this to be useful. You can also turn this on temporarily from the recent changes page (see [[Help:Tracking changes]]).
* ''Enhanced recent changes (JavaScript)'': Enhanced recent changes condenses edits into a per-page list. As indicated, this requires JavaScript to be enabled. See [[Help:Tracking changes]] for more information on this feature.

==Watchlist==

==Search==
Default settings for searches including how many results to display and how much context to show for each result.  Check the boxes next to the namespaces which you want to show up, the first time that you search for something.  You can override this when doing an actual search, by checking or unchecking the boxes at the bottom of the search results screen.

''Administrators'': To change the namespace default preferences for new users (or users who haven't changed their preferences yet), see {{mediawiki|Manual:$wgNamespacesToBeSearchedDefault}}

==Misc==
Other settings such as numbering and justification.

== See also ==
* [[Help:Skins]]

{{Languages|Help:Preferences}}

[[Category:Help|Preferences]]</text>
    <sha1>89670241783e0c976b12721468e5d6c5ec055edb</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Skins</title>
  <ns>12</ns>
  <id>27</id>
  <revision>
    <id>111</id>
    <parentid>110</parentid>
    <timestamp>2008-07-29T18:30:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1018" xml:space="preserve">{{PD Help Page}}

Clicking on the [[Special:preferences|my preferences]] link in the upper right while logged in then click on the '''Skin''' button to change your skin. You can also preview the skin by clicking the '''(preview)''' links next to each skin.

You can make changes to the current skin's {{mediawiki|Manual:Interface/Stylesheets|stylesheet}} file (CSS) by creating a subpage of your userpage, "[[Special:Mypage/monobook.css|User:Yourname/monobook.css]]" for example. This requires your site admin to have enabled this feature -- if it is, you will see advice text at the top of your custom CSS page about clearing your browser's cache.

{{admin tip|tip=To enable this feature, you have to set [http://www.mediawiki.org/wiki/Manual:%24wgAllowUserCss $wgAllowUserCss] to your {{mediawiki|Manual:LocalSettings.php|LocalSettings.php}}.}}


== See also ==
* [[Help:Preferences]]

{{Languages|Help:Skins}}

[[Category:Help|{{PAGENAME}}]]
[[Category:Special Pages|{{PAGENAME}}]]
[[Category:Subpage|{{PAGENAME}}]]</text>
    <sha1>9d3f0b32741f0e525a349b2ceb34d5b559979564</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Namespaces</title>
  <ns>12</ns>
  <id>28</id>
  <revision>
    <id>113</id>
    <parentid>112</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2088" xml:space="preserve">{{PD Help Page}}
Pages without a ':' in their name are in the main namespace. These are typically the bulk of the content pages in a wiki. Pages which aren't directly related to this core content, may go in other namespaces. These pages have a name of the form "''namespace'':''page''", for example this page is called "''{{NAMESPACE}}'':''{{PAGENAME}}''" (it is in the {{NAMESPACE}} namespace) 

Use of namespaces can vary from one wiki to another, but a typical scheme would be as follows:

;Help: Documentation about working with the wiki software.  This could be mirrored from outside sites, or locally written.
;Image: For descriptions of uploaded files or media files.  You shouldn't create these directly; they are created when you click the [[special:upload|Upload file]] link in the toolbox.
;Media: Use this namespace to link to uploaded files directly, rather than through the description pages.
;MediaWiki: Use this namespace to change the default system messages, [http://meta.wikimedia.org/wiki/Help:System_message See Help:System message on meta].
;Project: Information about this wiki; i.e. policies that apply here.  This namespace also has an alias, which is the name of the wiki installation.
;Talk: Each page has a corresponding ''discussion'' page.  This can be used for feedback/comments about that page, or other local notes that another group may want to associate with the page, without modifying the document directly, or for any other additional information to associate with the document.
;Template: This is used for meta-information that is to be transcluded into multiple documents, such as tags to mark the status of a document.
;User: For personal notes.  Each User has a corresponding user page for their own information.  Users can also create subpages, by using a / after their name.
;User_talk: The discussion page on a user's page can be used for leaving messages.  If this page is edited, the next time that user logs in they will see a box notifying them that they have new messages

{{Languages}}
[[Category:Help|Namespaces]]
[[Category:Namespace]]</text>
    <sha1>5533fbd6f904860fa0a5e1bc2cb7a36d02def267</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Special pages</title>
  <ns>12</ns>
  <id>30</id>
  <revision>
    <id>117</id>
    <parentid>116</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="694" xml:space="preserve">{{PD Help Page}}
'''Special pages''' are pages that are created by the software on demand. They are located in their own [[Help:Namespaces|namespace]] ''Special:'' and are not editable directly as other pages. 

Some special pages depend on the [[Help:Preferences|preferences]] that have been set by a user, e.g. the number of titles which is displayed on a user's [[Help:Watchlist|watchlist]].

==List of special pages==
Clicking the link ''[[Special:Specialpages]]'' will take you to a list of all special pages on a wiki. Such a link is often accessible in the [[toolbox]] on the left hand panel.

{{Languages|Help:Special pages}}
[[Category:Help|Special pages]]
[[Category:Special Pages| ]]</text>
    <sha1>8a0693444ca611845397ff18faef40f0cb412d12</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:External searches</title>
  <ns>12</ns>
  <id>31</id>
  <revision>
    <id>118</id>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1435" xml:space="preserve">{{PD Help Page}}
It is possible to create an external searches of a topic using key words using a template.

For example, this is something that would work for Google:
&lt;pre&gt;&lt;nowiki&gt;
&lt;span style="border: 1px solid #CCD5DB;"&gt;[[Image:GoogleIcon.PNG]] [http://www.google.com/search?hl=en&amp;safe=off&amp;q={{{1|Wiki}}}&amp;btnG=Search&amp;meta= {{{1|Google}}}]&lt;/span&gt;
==Usage==
Allows to establish a link to a search query at the Google search engine:
&lt;div style="display:table; width:auto;"&gt;&lt;pre&gt;
{{Google|Term1+Term2+Term3}}
&amp;lt;/pre&gt;&lt;/div&gt;
[[Category:Template|Google]]
&lt;/noinclude&gt;&lt;/nowiki&gt;&lt;/pre&gt;

The usage is very simple and easy to use. &lt;nowiki&gt;{{Google|firstTerm+Second+etc}}&lt;/nowiki&gt; 

It is also possible to do phrases by using %22Term1+Term2+etc%22

*External searches are useful where an article requires certain keywords to make an effective search.
*For the editor it allows making searches of web more quickly and painlessly.

Other applications of the template include searching Forums, for bug reports of the same type for software development wikis where the wiki and forum work together.

Note: Wikipedia has an [[Help:Links#Interwiki_links|interwiki prefix]] with a similar effect, so you can link to google results with &lt;nowiki&gt;[[Google:firstTerm+Second+etc]]&lt;/nowiki&gt;, although templates are still useful for linking other search engines.

{{languages|Help:External searches}}

[[Category:Help|External Searches]]
[[Category:Search]]</text>
    <sha1>1dc483e6bb93be6cd22b47414a11da91a53d70d4</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:User page</title>
  <ns>12</ns>
  <id>32</id>
  <revision>
    <id>121</id>
    <parentid>120</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3079" xml:space="preserve">{{PD Help Page}}

A '''user page''' is a page about a wiki user; someone who registered on the wiki, and is (most probably) a contributor. If you have registered, you can create your own user page. Your user page is linked in the top right. More importantly, others will see links to your user page from various places which assist wiki collaboration. This includes the 'Recent changes' and page 'history' displays (See [[Help:Tracking changes]]). You can also link to your user page within text of a wiki page, which is mainly useful on [[Help:Talk pages|talk pages]] when you sign your name.

== What to put on your user page ==
User pages are just as flexible as any other wiki page, and it's a page all about you, so generally people will leave you to freely write your user page in whatever format you like. Think of it as a 'profile' page. It's a feature to help other people know who you are, and to bring the online community closer together. You might like to mention where you are from and what your job is. You can also state what your main areas of interest are in relation to the topic of the wiki, and describe contributions you have made or are areas where you are interested in contributing.

=== User scratchpad / development area ===
You can use your user page as a scratchpad. An area for developing ideas without cluttering the main namespace. If subpages are enabled (See [[Help:Subpages]]), you may find them useful for creating sub pages under your user page. However you should avoid expending too much effort within your own area of the wiki. Be bold! Edit the main wiki articles! You can also use a shared [[Sandbox]] page for quick (non-permanent) wiki experimentation.

== Other people's user pages ==

As mentioned above, you will see links to other people's user pages, in various places throughout the wiki.

=== User Contributions ===
When viewing another person's user page, an additional link "''user contributions''" appears in the 'toolbox' area (bottom left). This takes you to a list of all of this user's wiki edits. Use this to get an idea of how prolific a contributor somebody is, or to track down edits made by a user who is causing trouble/making bad wiki edits.

=== Editing someone else's page ===
It's generally considered bad etiquette to rewrite or reword another person's user page. Editing is not disallowed, but you should avoid adding information (or especially opinions) which might be misinterpreted as coming from that user, in situations where this could potentially cause upset. Some types of edit are widely acceptable, and unlikely to cause upset:

* Fixing wiki links, when a page has been [[Help:Moving a page|moved]] or [[Help:Deleting a page|deleted]]
* Fixing broken external links
* Categorizing or fixing categories of user pages.

=== User talk pages ===
Every user page has an associated talk page; a "user talk page". This is a special kind of talk page, for leaving messages directed at a particular user. See [[Help:Talk pages#User Talk pages]].

{{Languages|Help:User page}}

[[Category:Help|{{PAGENAME}}]]</text>
    <sha1>3232bf6394faf849319685bdcd571e226196335d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Sysops and permissions</title>
  <ns>12</ns>
  <id>33</id>
  <revision>
    <id>123</id>
    <parentid>122</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2952" xml:space="preserve">{{PD Help Page}}
The way '''permissions''' are set-up on different wikis can vary, but in general...

== Soft security - There ''are'' no permissions ==

Wikis are often set up to be freely and openly editable. This means anyone can edit the pages, often without even registering/logging in. This is only possible because wikis offer a unique kind of "soft security". By making it very simple to monitor edits, and revert changes to retrieve an older version of a page, a wiki doesn't need to be very restrictive at all.

There ''are'' no permissions. Everyone is an administrator. You don't need permission to edit, and you are encouraged to "be bold", go forth and edit!

...at least that is the theory. In practice MediaWiki software does offer many options related to permissions.

== Sysops ==
By default MediaWiki provides extra functionality to a group of trusted users called 'sysops' (or known more generally as 'administrators') Most of the time this should go largely unnoticed by the normal users of a wiki community. Everyone can get involved in editing pages, and even undertaking drastic reorganisation of the wiki. The extra powers of a sysop user are intended for use in settling disputes and preventing repeated vandalism.

=== Who are the sysops? ===
You can find out who the sysops are at [[Special:ListUsers/sysop]]

=== What can a sysop do? ===
There are a number of extra features available to sysops. The key ones are as follows:

;Protecting and unprotecting pages, and editing protected pages
:'Protecting' a page prevents normal users from editing the page at all. There are several reasons why a particular page might be protected. For more information see [[Help:Protected pages]]. For sysop information see [[Help:Protecting and unprotecting pages]]

;Deleting pages, and undeleting.
:A page can be deleted semi-permanently, such that it is no longer available (even in the page histories) for normal users. Normal users do not have this power. See [[Help:Deleting a page]]. For sysop information see [[Help:Sysop deleting and undeleting]].

;Blocking a user or IP address, and unblocking them.
:Users can be blocked from the wiki. This is a useful way of keeping out persistent vandals. Users are identified by their registered user name, or by I.P. address, and can be blocked permanently, or just short length of time to give them a "cooling off" period. See [[Help:Blocking users]]

;Patrolling, and seeing patrolled edits.
:This is a way of coordinating with other sysops, to ensure that every edit of the wiki has been checked over by a trusted user. See [[Help:Patrolled edits]]

== Bureaucrats ==
Another level of permissions within a default MediaWiki set-up, is the 'bureaucrat' group.

The main thing a bureaucrat can do, which 'sysop' cannot, is '''promote users to be sysops''' (and demote sysops to normal users).  See [[Help:Assigning permissions]]


== See Also ==

* {{mediawiki|meta:Help:Administration}}</text>
    <sha1>cfc47c3d849c3698731add010b148004356f406f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Protecting and unprotecting pages</title>
  <ns>12</ns>
  <id>34</id>
  <revision>
    <id>124</id>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="735" xml:space="preserve">{{PD Help Page}}
'''Protecting and unprotecting pages''' is very straightforward, but these operations require [[Help:Sysops and permissions|sysop permissions]].

You can designate a page as a [[Help:Protected pages|protected page]] by clicking the 'Protect page' tab, and supplying a comment (a brief textual description of why you are protecting the page)

There are several reasons why a particular page might be protected. Typically a protected page is one which has been repeatedly targeted with vandalism, or where it is believed that any vandalism would have a unusually severe impact. However there are also many good reasons for ''not'' protecting pages. As a sysop you must make this choice, and wield your power responsibly.</text>
    <sha1>801360d771ebc565184284d49c1f9dd1ac883799</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Patrolled edits</title>
  <ns>12</ns>
  <id>36</id>
  <revision>
    <id>129</id>
    <parentid>128</parentid>
    <timestamp>2008-07-29T18:30:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2388" xml:space="preserve">{{PD Help Page}}
&lt;div style="float:right;"&gt;__TOC__&lt;/div&gt;
'''Patrolled edits''' are a feature which allows specific users to mark items in recent changes as having been "patrolled" or "approved". By default this is only available if you have [[Help:Sysops and permissions|sysop permissions]]

This feature is useful when reviewing recent changes for undesirable edits, link spam and vandalism. This allows people (those who can see it) to coordinate their patrolling activity, such that edits gets checked over once, but with less wasted effort (different people checking the same edit)

== Marking edits as patrolled ==

; To mark an edit as patrolled

#Access [[Special:Recentchanges]]
#:Changes which are not patrolled will be indicated with a red exclamation mark
#Click the ({{mediawiki|m:Help:Diff|diff}}) link next to an edit
#To mark the edit as patrolled, click the ''mark as patrolled'' link

== Customization ==

=== Enabling/disabling ===

Patrolled edits are enabled by default in MediaWiki 1.4. In MediaWiki 1.5 and later, set '''$wgUseRCPatrol''' in {{mediawiki|Manual:Configuration settings|LocalSettings.php}}.

&lt;code&gt;$wgUseRCPatrol = true;&lt;/code&gt;

=== Permissions ===

==== 1.4 ====

In MediaWiki 1.4, patrolled edits are enabled for all users. To restrict this to sysops, set '''$wgOnlySysopsCanPatrol''' in {{mediawiki|Manual:Configuration settings|LocalSettings.php}}.

&lt;code&gt;$wgOnlySysopsCanPatrol = true;&lt;/code&gt;

==== 1.5+ ====

In MediaWiki 1.5 and later, patrolled edits are enabled for sysops. Use the '''{{mediawiki|Manual:$wgGroupPermissions|$wgGroupPermissions}}''' configuration variable for this.

For instance, to create a ''patrollers'' group:

&lt;code&gt;$wgGroupPermissions['patrollers']['patrol'] = true;&lt;/code&gt;

=== Automatic patrolling ===
In MediaWiki 1.6 through 1.8, there is a [[Help:preferences|user preference]] available to users who are able to mark edits as patrolled. When set, this causes their edits to be patrolled automatically.

This option is not available if patrolled edits are switched off.

In MediaWiki 1.9 this user preference has been removed and replaced by a new "autopatrol" right, assigned only to sysops by default. Also, users cannot mark their own edits as patrolled.

=== Marker ===

The formatting of the unpatrolled edit marker can be altered using CSS.

{{Languages|Help:Patrolled edits}}
[[Category:Help|Patrolled edits]]</text>
    <sha1>fbab63b50eb940806dad4ee59715db5404692f52</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Assigning permissions</title>
  <ns>12</ns>
  <id>37</id>
  <revision>
    <id>130</id>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3559" xml:space="preserve">{{PD Help Page}}
"'''Assigning permissions'''" means granting users extra rights within the wiki software (or revoking these rights). This is done by going to the [[Special:UserRights]] page, and adding users into a "group" which has specific rights. The first thing to note however, is that this action requires special permissions itself! 

{{Admin tip|tip=See {{mediawiki|Manual:User rights}} and {{mediawiki|Manual:User rights management}} for information on fine grained permissions tweaks, and how to define new groups, or adjust existing groups to give different rights.

Note that this help page describes the '''default''' MediaWiki configuration, but every aspect of permissions is highly customisable with server config settings. You may wish to rewrite this help page to reflect your wiki configuration}}

== Bureaucrats == 

By default, you will need to be a 'Bureaucrat' (in the 'Bureaucrat' group) before you can access the [[Special:UserRights]] page. Other users can always contact one of the bureaucrats to request a change of permissions. Find out who these people are at [[Special:ListUsers/bureaucrat]]. In a small wiki there might typically be only one such user.

== Promoting users to Sysops and Bureaucrats ==

The [[Special:UserRights]] page allows you (if you have access) to set which groups a user is in. A common task would be to put a user into the 'Sysop' group. This will grant the user various extra rights, such as deleting pages, and blocking users. See [[Help:Sysops and permissions]] for more details.

Obviously giving a user such rights implies that you '''trust''' the user, both in terms of being non-malicious, and also as somebody with sufficient competence in using the wiki software, and in dealing with the wiki community. People hoping to become sysops should read [[Help:Sysops and permissions]]. However it should be noted that actions of a sysop user are (almost) entirely reversible, by other sysop users, and so it can be a good idea to dish out these extra permissions to a number of users in order to
* spread the workload of day-to-day sysop operations such as blocking vandals and deleting pages.
* make things more democratic, and decrease any perception of a single dictator running the community
* allow competent users the power they need to make progress with wiki refactoring.
* reward valued contributors/community members

== Processes ==
If you have many sysops, you may start to need documented processes governing their actions. e.g. when should a page be protected versus leaving it unprotected? You may even reach the point where you need a documented procedure for deciding who gets to be a sysop, and who should have their sysop rights revoked. To manage all of this, you may wish to promote several users into the 'Bureaucrat' group (a smaller number of your most trusted users) to spread the workload managing the promoting/demoting of sysops.  On some large wikis, users are voted in by other users before they are granted extra permissions, and sysops have their rights revoked by a committee who investigate accusations of misconduct. Such processes are unlikely to be necessary in anything but the largest of wiki communities.

== Other permissions ==
Beyond promoting/demoting of Sysops and Bureaucrats, you can also allow a user to operate as a 'bot', meaning their edits do not show up on recent changes.

== See also ==
* {{mediawiki|Manual:User_rights_management|Manual:User rights management}}

{{Languages|Help:Assigning permissions}}
[[Category:Help|Assigning permissions]]</text>
    <sha1>4bf7b9e2765c27107afdfa9dbf28ad71b3e4ba63</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Help:Linked images</title>
  <ns>12</ns>
  <id>38</id>
  <revision>
    <id>133</id>
    <parentid>132</parentid>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7064" xml:space="preserve">{{PD Help Page}}

[[Help:Images|Images]] on a MediaWiki wiki are designed to link to the description page, so that licensing information, upload history, contributors, and full resolution versions are immediately available to the user when he or she clicks an image. In fact, MediaWiki is designed to prevent manual manipulation of images in wikicode which may circumvent this operation: The '''&lt;tt&gt;&amp;lt;img&amp;gt;&lt;/tt&gt;''' tag is specifically not whitelisted in the {{mediawiki|Manual:Sanitizer.php|Sanitizer}}, nor is the '''&lt;tt&gt;background-image&lt;/tt&gt;''' CSS attribute.

However, there are several workarounds for those that require them.

==Vanilla install==
If you only have sysop access to the Wiki, these are your best options.

===Site CSS===
The most simplistic method, if your requirements for external images are specialized (that is, restricted to one page or one image), is to add a CSS rule to your MediaWiki:Common.css (or other CSS files, such as MediaWiki:Skinname.css or /skins/skinname/main.css, etc) giving child links of a certain class of object a background image. This method also has some security, as it requires editing the site-wide CSS files, meaning only sysops have access to modify the image shown. 

For example (red sections are parts to configure for each image):

In MediaWiki:Common.css:
 '''&lt;tt&gt;.imagelink_&lt;span style="color:red;"&gt;somename&lt;/span&gt; a {
   width:&lt;span style="color:red;"&gt;100&lt;/span&gt;px;
   height:&lt;span style="color:red;"&gt;100&lt;/span&gt;px;
   display:block;
   text-decoration:none;
   background-image: url("&lt;span style="color:red;"&gt;&lt;nowiki&gt;http://fullurltoimage&lt;/nowiki&gt;&lt;/span&gt;") 
 }&lt;/tt&gt;'''
In your wikicode:
 '''&lt;tt&gt;&amp;lt;div class="imagelink_&lt;span style="color:red;"&gt;somename&lt;/span&gt;"&amp;gt;&lt;nowiki&gt;[[&lt;/nowiki&gt;&lt;span style="color:red;"&gt;Some link&lt;/span&gt;|&amp;amp;nbsp;&lt;nowiki&gt;]]&lt;/nowiki&gt;&amp;lt;/div&amp;gt;&lt;/tt&gt;'''

This would give the link the background image specified, as well as the width and height of the image (which you have to set manually). To find the location of an uploaded file, go to the image description page and click the image itself, and copy the image location in the address bar. 

For example on [[:Image:Wiki.png]], the image location is http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png (location format will differ depending on local settings), and the width and height would be set to 135px and 135px. So to make a link to the main page here using that logo, one would add to [[MediaWiki:Common.css]]:
&lt;pre&gt;.imagelink_wikilogo a {
  width:135px;
  height:135px;
  display:block;
  text-decoration:none;
  background-image: url("http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png") 
}&lt;/pre&gt;
And then use the wikicode:
&lt;pre&gt;&lt;div class="imagelink_wikilogo"&gt;[[MediaWiki|&amp;amp;nbsp;]]&lt;/div&gt;&lt;/pre&gt;

Which would give you:
&lt;div class="imagelink_wikilogo"&gt;[[MediaWiki|&amp;nbsp;]]&lt;/div&gt;

You can also use a thumbnail of an image, but make sure the thumbnail is being used elsewhere, as most installations are not configured to generate thumbnails on demand.

===Inline CSS===
You can also attempt to superimpose an invisible link over an image via CSS, such as is done in [[Template:Click]]. An example of a typical click template is:
&lt;pre&gt;&lt;div style="position: relative; width: {{{width}}}; height: {{{height}}}; overflow: hidden;"&gt;
&lt;div style="position: absolute; top: 0px; left: 0px; font-size: 100px; overflow: hidden; line-height: 100px; z-index: 3;"&gt;[[{{{link}}}|&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;]]&lt;/div&gt;
&lt;div style="position: absolute; top: 0px; left: 0px; z-index: 2;"&gt;[[Image:{{{image}}}|{{{width}}}|{{{link}}}]]&lt;/div&gt;
&lt;/div&gt;&lt;/pre&gt;

Known problems: It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations.  The technique of using [[wikipedia:CSS|CSS]] to change page content also completely breaks an article's [[wikipedia:web accessibility|web accessibility]] by contravening a [[wikipedia:WAI|WAI]] priority-one checkpoint.[http://www.w3.org/TR/WAI-WEBCONTENT/#tech-order-style-sheets]

===Redirect===
A less elegant trick is to make the image description page a redirect to the target. So for example [[:Image:Wiki.png]] would be changed to content:
&lt;pre&gt;#REDIRECT [[MediaWiki]]&lt;/pre&gt;
There are several disadvantages to this:
* It doesn't always work, some installations/versions have internamespace redirects disabled.
* The image appears at the top of the article. This is because MediaWiki redirects aren't really redirects, they simply bring the target page's data to the current URL, but on image description pages this is done after the image itself is shown.
* It can only be done once per image.

==Native with configuration change==
If you have server access, but do not want to install any extensions, these solutions may work for you.
===External image syntax===
If you enable {{mediawiki|Manual:$wgAllowExternalImages|$wgAllowExternalImages}} (which allows external images from any domain) or {{mediawiki|Manual:$wgAllowExternalImagesFrom|$wgAllowExternalImagesFrom}} (which restricts the list of domains), anyone can then easily create an "external" link to an "external" image. External simply means: using the full URL rather than a local link, so you can link locally, but you need to use the full URL. The plainlinks class is used to remove the "external link" icon:

 &amp;lt;span class="plainlinks"&amp;gt;&lt;span style="color:red;"&gt;&lt;nowiki&gt;[http://linktopage http://linktoimage]&lt;/nowiki&gt;&lt;/span&gt;&amp;lt;/span&amp;gt;

So for example, were external images allowed here, you could link to the {{mediawiki|MediaWiki|main page}} with http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png using wikicode like:

 &amp;lt;span class="plainlinks"&amp;gt;&lt;nowiki&gt;[{{fullurl:MediaWiki}} http://upload.wikimedia.org/wikipedia/mediawiki/b/bc/Wiki.png]&lt;/nowiki&gt;&amp;lt;/span&amp;gt;

This has the disadvantage of not registering the link, or the image use, as well as not being easily portable to forks and mirrors.

===Raw HTML===
If you enable {{mediawiki|Manual:$wgRawHtml|$wgRawHtml}}, you can use '''&lt;tt&gt;&amp;lt;img&amp;gt;&lt;/tt&gt;''' tags freely, but this method is highly insecure.

There are, however, some extensions to make it safer, see {{mediawiki|Manual:$wgRawHtml#Related_Extensions}} for details.

==via Extension==
If you are willing to install an extension, several extensions have been created to address this issue:
*{{mediawiki|Extension:ImageMap}} - advanced image shape-link extension, uses the html USEMAP features ''(xml tag)''
*{{mediawiki|Extension:LinkedImage}} - image links ''(XML tag)''
*{{mediawiki|Extension:Icon}} - image links ''(parser function)''

Or you can invent your own linked image syntax, by writing an extension that registers it as a parser hook. See {{mediawiki|Manual:Tag extensions}} for information on extending MediaWiki syntax.

==Other options==
If you want, you can do some more drastic things, such as modify /includes/Sanitizer.php (where the HTML tag whitelist is), and add &amp;lt;img /&amp;gt; to the list of allowed tags.

==See also==
*[[Help:Contents]]
*[[Help:Links]]
*[[Help:Images]]

[[Category:Help|Linked images]]</text>
    <sha1>2b8be06700b987868ef7ddbdbb22f3a1d5473c95</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Help</title>
  <ns>14</ns>
  <id>39</id>
  <revision>
    <id>135</id>
    <parentid>134</parentid>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="945" xml:space="preserve">[[Image:PD-Help icon.png|right|100px|Your help is welcomed. Writers needed.]]

[[:Category:Help]] is for MediaWiki generic site user help. Only pages in namespace "Help:" should be in this category. Note that all pages in namespace "Help:" are released into the [http://en.wikipedia.org/wiki/Public_domain Public domain] so that they can be easily imported into any MediaWiki instance regardless of the specific wiki's own license. See '''[http://www.mediawiki.com/wiki/Project:PD_Help Project:PD Help]''' if you want to help us.

''Every single English-language page within the set of public domain Help pages should directly be categorized &lt;nowiki&gt;[[Category:Help]]&lt;/nowiki&gt; (additionally putting pages in other categories to provide further sorting is possible). This is needed because of later half-automated creation of the PD Help package from this category.''

The front page is '''[[Help:Contents]]'''

{{Languages}}

{{Help/Categories}}</text>
    <sha1>16d02f422c733e090aa7cdcc64944e78c5c470a7</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:PD Help Page</title>
  <ns>10</ns>
  <id>40</id>
  <revision>
    <id>136</id>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="869" xml:space="preserve">&lt;div style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em 1em 0.5em 0.7em; margin:0.5em 0.5em 0.5em 0.5em; background-color:#FFFFFF;font-size:95%; vertical-align:middle;"&gt;
{|
| style="padding: 0.4em 0.2em 0 0;" valign="top" | [[Image:PD-icon.svg|20px|left|PD]] || '''Important note:''' When you edit this page, you agree to release your contribution into the [[:en:Public domain|public domain]]. If you don't want this or can't do this because of license restrictions, please don't edit. This page is one of the [[Project:PD help|Public Domain Help Pages]], which can be freely copied into fresh wiki installations and/or distributed with MediaWiki software; see [[Help:Contents]] for an overview of all pages. See [[Help:Copying]] for instructions.
|}&lt;/div&gt;
&lt;noinclude&gt;{{Languages|Template:PD Help Page}}[[Category:License templates|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>d53b30bd2e06ddcd3efa28ea2c533e849c910212</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Template:PD</title>
  <ns>10</ns>
  <id>41</id>
  <revision>
    <id>138</id>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="526" xml:space="preserve">&lt;br style="clear:both;" /&gt;
{| align="center"  style="width:95%; background-color:#f8f8f8; border:2px solid #e0e0e0;  padding:5px;"
|-
| [[Image:PD-icon.svg|50px|PD]]
| align="center" | ''This file has been released into the '''[[w:public domain|public domain]]''' by the [[w:Copyrights|copyright]] holder, its copyright has expired, or it is ineligible for copyright. This applies worldwide.''
|}
&lt;includeonly&gt;[[Category:PD images|{{PAGENAME}}]]&lt;/includeonly&gt;
&lt;noinclude&gt;[[Category:License templates|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>af4ac99baa3f51e3d18c6d8b08a62beee1fc4ad4</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Mediawiki</title>
  <ns>10</ns>
  <id>42</id>
  <revision>
    <id>141</id>
    <parentid>140</parentid>
    <timestamp>2008-07-29T18:30:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="767" xml:space="preserve">{{ #ifeq:
  {{SERVERNAME}}
| www.mediawiki.org
| [[{{{1}}}|{{{2|{{{1}}}}}}]]
| [http://www.mediawiki.org/wiki/{{urlencode:{{{1}}}}} {{{2|{{{1}}}}}}]
}}&lt;noinclude&gt;
----
This template links to a page on mediawiki.org from the [[Help:Contents|Help pages]]. The template has two parameters:
# Pagename
# (optional) Link description

{{ #ifeq:
{{SERVERNAME}}
| www.mediawiki.org
| This is so that the public domain help pages - which can be freely copied and included in other sites - have correct links to Mediawiki:
* on external sites, it creates an external link
* on Mediawiki, it creates an internal link

'''All''' links from the Help namespace to other parts of the mediawiki.org wiki should use this template.}}

[[Category:Info templates|MediaWiki]]
&lt;/noinclude&gt;</text>
    <sha1>837244978aea6e95acaa9c122f9e4dd31b4a9a9d</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Note</title>
  <ns>10</ns>
  <id>43</id>
  <revision>
    <id>142</id>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1250" xml:space="preserve">{{#if: {{{1|}}}|&lt;table cellspacing="0" cellpadding="0" border="0" style="background: transparent;"&gt;&lt;tr&gt;&lt;td nowrap="true" valign="top"&gt;}}[[Image:Bulbgraph.png|18px|Note]]{{#if: {{{1|}}}|&lt;/td&gt;&lt;td valign="top" style="padding-left:0.5em;"&gt;}} '''Note''': {{#if: {{{1|}}}|&lt;/td&gt;&lt;td valign="top" style="padding-left:0.5em;"&gt;{{{1|}}}&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;}}&lt;noinclude&gt;

== Usage ==

=== Method 1 ===

The following displays the note icon and the word 'Note:'.  You can follow this with whatever text/images/markup you like.
 &lt;nowiki&gt;{{note}}&lt;/nowiki&gt; Here is my note.

{{note}} Here is my note.

=== Method 2 ===
The following includes the text passed to the template, and uses a table to stop the text flowing round the icon.
 &lt;nowiki&gt;{{note|Here is a long note, which is sufficiently wordy to run onto a second line, 
 which would normally cause it to wrap round the icon, but because we passed it as a parameter 
 it keeps its left alignment straight.}}&lt;/nowiki&gt; 

{{note|Here is a long note, which is sufficiently wordy to run onto a second line, which would normally cause it to wrap round the icon, but because we passed it as a parameter it keeps its left alignment straight.}}

{{Languages|Template:Note}}

[[Category:Templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>62ff9f841d06cefb1453527307832ef1c075f584</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Admin tip</title>
  <ns>10</ns>
  <id>44</id>
  <revision>
    <id>149</id>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="329" xml:space="preserve">&lt;onlyinclude&gt;&lt;div style="font-color:#535068; border:solid 1px #A8A8A8; padding:0.5em 1em 0.5em 0.7em;  margin:0.5em 0em; background-color:#FFFFFF;font-size:85%;"&gt;
{| 
|[[Image:Tools.svg|20px]]
|'''Tip for wiki admins:''' {{{tip}}}
|}
&lt;/div&gt;&lt;/onlyinclude&gt;

{{Languages|Template:Admin tip}}
[[Category:Info templates|{{PAGENAME}}]]</text>
    <sha1>dbf57fcd2824aedd3cfcb0b3acd35d6c54fae80a</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Prettytable</title>
  <ns>10</ns>
  <id>45</id>
  <revision>
    <id>152</id>
    <parentid>151</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="257" xml:space="preserve">border="2" width="{{{width|100%}}}" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;{{{style|}}}"
&lt;noinclude&gt;[[Category:Utility templates|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>736365ee298b77f8f22f6964c39531e48d0ceaba</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Hl2</title>
  <ns>10</ns>
  <id>46</id>
  <revision>
    <id>153</id>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="84" xml:space="preserve">bgcolor="#A7C1F2" &lt;noinclude&gt;[[Category:Utility templates|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>3afc2b03bfd3f4c68c0fbb45b7ef52d642b0f8df</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Hl3</title>
  <ns>10</ns>
  <id>47</id>
  <revision>
    <id>156</id>
    <parentid>155</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="98" xml:space="preserve">bgcolor="#8DA7D6" color="black" &lt;noinclude&gt;[[Category:Utility templates|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>aef9e6074aae2d0d93e1455d3217117c1a49ef1b</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Thankyou</title>
  <ns>10</ns>
  <id>48</id>
  <revision>
    <id>158</id>
    <parentid>157</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="356" xml:space="preserve">&lt;div class="noprint" style="float:right; border:1px solid blue;width:200px;background-color:#fff;padding:3px;"&gt;
[[Image:Example.jpg|left|80px|Example sunflower image]] '''A little thank you...''' &lt;br /&gt;&lt;small&gt;for {{{1}}}. &lt;br /&gt;hugs, {{{2}}}&lt;/small&gt;
&lt;/div&gt;
&lt;noinclude&gt;
{{Languages|Template:Thankyou}}
[[Category:Template examples|{{PAGENAME}}]]&lt;/noinclude&gt;</text>
    <sha1>b8ede1041a2ef0d6b248ffc3d97a1e413af94f45</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Click</title>
  <ns>10</ns>
  <id>49</id>
  <revision>
    <id>160</id>
    <parentid>159</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="397" xml:space="preserve">&lt;includeonly&gt;{{#tag:imagemap|
Image:{{{image|}}} {{!}} {{#iferror: {{#expr:{{{width}}} &gt; 0 }} |{{{width|}}}|{{{width}}}{{#if:{{{height|}}}|{{#iferror: {{#expr:{{{height}}} &gt; 0 }}||x{{{height}}}}}px|px}}}} {{!}} {{{title|{{{link|}}}}}}
default [[{{{link|Main Page}}}|{{{title|{{{link|}}}}}}]]
desc {{{desc|none}}}
}}&lt;/includeonly&gt;&lt;noinclude&gt;
{{doc}}
[[Category:Templates|{{PAGENAME}}]]
&lt;/noinclude&gt;</text>
    <sha1>e5a89749436d29420a361146b552b3626e767745</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Languages</title>
  <ns>10</ns>
  <id>50</id>
  <revision>
    <id>162</id>
    <parentid>161</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6265" xml:space="preserve">== Template ==

&lt;onlyinclude&gt;&lt;div class="LanguageLinks"&gt;
&lt;table width="100%"&gt;
&lt;tr valign="top" style="background: #EEF3E2"&gt;
&lt;td style="width: 25px; padding-left: 0.5em;"&gt;[[Image:Geographylogo.png|25px|Languages]]&lt;/td&gt;
&lt;td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #aaaaaa;"&gt;'''[[Project:Language policy|Languages]]:'''&amp;nbsp;&lt;/td&gt;&lt;td style="padding: 1px 1em 0; background: #F6F9ED;"&gt;
'''[[{{{1|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}|English]]'''
{{Languages/Lang|af|{{{1|}}}}}
{{Languages/Lang|ar|{{{1|}}}}}
{{Languages/Lang|az|{{{1|}}}}}
{{Languages/Lang|bcc|{{{1|}}}}}
{{Languages/Lang|bg|{{{1|}}}}}
{{Languages/Lang|br|{{{1|}}}}}
{{Languages/Lang|ca|{{{1|}}}}}
{{Languages/Lang|cs|{{{1|}}}}}
{{Languages/Lang|de|{{{1|}}}}}
{{Languages/Lang|el|{{{1|}}}}}
{{Languages/Lang|es|{{{1|}}}}}
{{Languages/Lang|fa|{{{1|}}}}}
{{Languages/Lang|fi|{{{1|}}}}}
{{Languages/Lang|fr|{{{1|}}}}}
{{Languages/Lang|gu|{{{1|}}}}}
{{Languages/Lang|he|{{{1|}}}}}
{{Languages/Lang|hu|{{{1|}}}}}
{{Languages/Lang|id|{{{1|}}}}}
{{Languages/Lang|it|{{{1|}}}}}
{{Languages/Lang|ja|{{{1|}}}}}
{{Languages/Lang|ko|{{{1|}}}}}
{{Languages/Lang|ksh|{{{1|}}}}}
{{Languages/Lang|mr|{{{1|}}}}}
{{Languages/Lang|ms|{{{1|}}}}}
{{Languages/Lang|nl|{{{1|}}}}}
{{Languages/Lang|no|{{{1|}}}}}
{{Languages/Lang|oc|{{{1|}}}}}
{{Languages/Lang|pl|{{{1|}}}}}
{{Languages/Lang|pt|{{{1|}}}}}
{{Languages/Lang|ro|{{{1|}}}}}
{{Languages/Lang|ru|{{{1|}}}}}
{{Languages/Lang|si|{{{1|}}}}}
{{Languages/Lang|sq|{{{1|}}}}}
{{Languages/Lang|sr|{{{1|}}}}}
{{Languages/Lang|sv|{{{1|}}}}}
{{Languages/Lang|th|{{{1|}}}}}
{{Languages/Lang|tr|{{{1|}}}}}
{{Languages/Lang|uk|{{{1|}}}}}
{{Languages/Lang|vi|{{{1|}}}}}
{{Languages/Lang|yue|{{{1|}}}}}
{{Languages/Lang|zh|{{{1|}}}}}
{{Languages/Lang|zh-hans|{{{1|}}}}}
{{Languages/Lang|zh-hant|{{{1|}}}}}
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/div&gt;&lt;/onlyinclude&gt;

== Syntax ==
 &lt;nowiki&gt;{{Languages|PageName}}&lt;/nowiki&gt;

* '''PageName''' (optional) - the name of the page to display language links for.  If omitted then the English version of the current page is used.  This parameter can normally be omitted, as it is only required if you want to link to a page other than the one you place the template on, which is very uncommon.  If this parameter is used on a sub-page make sure you supply the root name, not the full page name (e.g. on [[MediaWiki/fr]] you would need to use &lt;code&gt;&lt;nowiki&gt;{{Languages|MediaWiki}}&lt;/nowiki&gt;&lt;/code&gt; and not &lt;code&gt;&lt;nowiki&gt;{{Languages|MediaWiki/fr}}&lt;/nowiki&gt;&lt;/code&gt;).

== Usage ==

The template should only be placed on pages that exist in more than one language, and it should be placed in the same location on each translation of the page.

The English version of a page is always the main version, with all other languages as sub-pages, named using the appropriate language code (see below). 

For example, on the Main Page you would include the text &lt;code&gt;&lt;nowiki&gt;{{Languages}}&lt;/nowiki&gt;&lt;/code&gt;, both on [[Main Page]] itself, and on each of its language sub-pages.  The template automatically creates links to any language sub-pages that exist, e.g. &lt;tt&gt;Main Page/ja&lt;tt&gt;, &lt;tt&gt;Main Page/fr&lt;/tt&gt;, and ignores non-existant languages.

See [[Project:Language policy]] for further details about translating pages.

== Supported languages ==
This shows you the name of each language's sub-page (using ''Main Page'' as an example). Other languages may be added easily as necessary.  Please use the appropriate [[meta:List of Wikipedias|prefix, as used on Wikipedia]] when adding a new language.  Please do ''not'' add languages for which no pages exist yet, as this will increase the time needed to include the template without adding any benefit (languages are only displayed to the user when the relevant page exists).

The link on the language names goes to the Wikipedia in that language. '''If no Wikipedia in your language exists, do not add pages in that language to MediaWiki.org!'''  This wiki is not the place for language advocacy - please go through the correct channels, and once your language has a Wikipedia then please return to add content here.

{| border="1" cellpadding="5"
! Page Name || Language 
|-
| Main Page || [[:en:|English]]
|-
| Main Page'''/af''' || [[:af:|Afrikaans]]
|-
| Main Page'''/ar''' || [[:ar:|Arabic]]
|-
| Main Page'''/az''' || [[:az:|Azerbaijani]]
|-
| Main Page'''/bcc''' || Southern Balochi
|-
| Main Page'''/bg''' || [[:bg:|Bulgarian]]
|-
| Main Page'''/br''' || [[:br:|Breton]]
|-
| Main Page'''/ca''' || [[:ca:|Catalan]]
|-
| Main Page'''/cs''' || [[:cs:|Czech]]
|-
| Main Page'''/de''' || [[:de:|German]]
|-
| Main Page'''/el''' || [[:el:|Greek]]
|-
| Main Page'''/es''' || [[:es:|Spanish]]
|-
| Main Page'''/fa''' || [[:fa:|Persian]]
|-
| Main Page'''/fi''' || [[:fi:|Finnish]]
|-
| Main Page'''/fr''' || [[:fr:|French]]
|-
| Main Page'''/gu''' || [[:gu:|Gujarati]]
|-
| Main Page'''/he''' || [[:he:|Hebrew]]
|-
| Main Page'''/hu''' || [[:hu:|Hungarian]]
|-
| Main Page'''/id''' || [[:id:|Indonesian]]
|-
| Main Page'''/it''' || [[:it:|Italian]]
|-
| Main Page'''/ja''' || [[:ja:|Japanese]]
|-
| Main Page'''/ko''' || [[:ko:|Korean]]
|-
| Main Page'''/ksh''' || [[:ksh:|Kölsch]]
|-
| Main Page'''/mr''' || [[:mr:|Marathi]]
|-
| Main Page'''/ms''' || [[:ms:|Malay]]
|-
| Main Page'''/nl''' || [[:nl:|Nederlands]]
|-
| Main Page'''/no''' || [[:no:|Norwegian]]
|-
| Main Page'''/oc''' || [[:oc:|Occitan]]
|-
| Main Page'''/pl''' || [[:pl:|Polish]]
|-
| Main Page'''/pt''' || [[:pt:|Portugese]]
|-
| Main Page'''/ro''' || [[:ro:|Romanian]]
|-
| Main Page'''/ru''' || [[:ru:|Russian]]
|-
| Main Page'''/si''' || [[:si:|Sinhalese]]
|-
| Main Page'''/sq''' || [[:sq:|Albanian]]
|-
| Main Page'''/sr''' || [[:sr:|Serbian]]
|-
| Main Page'''/sv''' || [[:sv:|Swedish]]
|-
| Main Page'''/th''' || [[:th:|Thai]]
|-
| Main Page'''/tr''' || [[:tr:|Turkish]]
|-
| Main Page'''/uk''' || [[:uk:|Ukrainian]]
|-
| Main Page'''/vi''' || [[:vi:|Vietnamese]]
|-
| Main Page'''/yue''' || [[:zh-yue:|Cantonese]]
|-
| Main Page'''/zh''' || [[:zh:|Chinese]]
|-
| Main Page'''/zh-hans''' || Chinese (Simplified)
|-
| Main Page'''/zh-hant''' || Chinese (Traditional)
|}

== Example ==
Here is how the language bar looks on the [[MediaWiki]] page:
{{Languages|MediaWiki}}
[[Category:Language templates]]</text>
    <sha1>91932c923a58fd1c8eb59ee1bd75cc3e00e1a311</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Template:Languages/Lang</title>
  <ns>10</ns>
  <id>51</id>
  <revision>
    <id>164</id>
    <parentid>163</parentid>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="979" xml:space="preserve">&lt;includeonly&gt;{{#ifexist: {{#if: {{{2|}}} | {{{2}}} | {{#if: {{NAMESPACE}} | {{NAMESPACE}}:}}{{BASEPAGENAME}}}}/{{{1}}} | &amp;nbsp;&amp;bull;&amp;nbsp;&lt;span lang="{{{1}}}"&gt;{{#if: {{{2|}}}|[[{{{2}}}/{{{1}}}|{{#language:{{{1}}}}}]]| [[:{{NAMESPACE}}:{{BASEPAGENAME}}/{{{1}}}|{{#language:{{{1}}}}}]]}}&lt;/span&gt;|&lt;span&gt;&lt;/span&gt;}}&lt;/includeonly&gt;&lt;noinclude&gt;
== Template ==
''This sub-template doesn't display properly when not included.  Please see [[Template:Languages]] for the complete version.''

== Usage ==

This template is designed to simplify [[Template:Languages]], by allowing a simpler syntax for adding new languages.  Each language is included by calling this template with the following parameters:

* '''Language code''' (e.g. fr)
* (optional) '''Page name''' - if not supplied the page is automatically worked out based on where the language template is included.

This template should not be used anywhere except in the Languages template.
[[Category:Language templates]]
&lt;/noinclude&gt;</text>
    <sha1>6671f7b8827f52aa4015a63f6d0daeb0b19f83fd</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:Example.jpg</title>
  <ns>6</ns>
  <id>52</id>
  <revision>
    <id>165</id>
    <timestamp>2008-07-29T18:30:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="605" xml:space="preserve">----
Note: This image is used as the example image when you use the edit toolbar (English default installation of MediaWiki).
----
* '''Description:''' Sunflowers in Fargo, North Dakota, U.S.
* '''Source:''' [http://www.ars.usda.gov/is/graphics/photos/k5751-1.htm www.ars.usda.gov] (cropped and reworked a bit)
* '''Author:''' Bruce Fritz
* '''Licensing:''' ''This image is in the '''public domain''' because it contains materials that originally came from the Agricultural Research Service, the research agency of the United States Department of Agriculture.''

{{PD}}
[[Category:Documentation examples]]</text>
    <sha1>5fe21b73d2a4d0f4c6339a9079643b3eae534736</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:Example-white-bg.jpg</title>
  <ns>6</ns>
  <id>53</id>
  <revision>
    <id>168</id>
    <parentid>167</parentid>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="150" xml:space="preserve">== Summary ==
Adapted version of [[:Image:Example.jpg]], to have a white background at the edges. To appear on [[Help:Images]]
== Licensing: ==
{{PD}}</text>
    <sha1>6d81ebe95954fd7476eac3326d811fd46fc4d283</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:PD-Help icon.png</title>
  <ns>6</ns>
  <id>54</id>
  <revision>
    <id>169</id>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="381" xml:space="preserve">* Icon for the [[Project:PD Help|Public Domain Help Pages]] on MediaWiki.org
* Logo combined by [[User:Bdk|&lt;span style="color:#116611"&gt;:Bdk:&lt;/span&gt;]] using 
::[[commons:Image:PD-icon.svg|PD-icon.svg]] (''public domain'') and 
::a reworked version of [[commons:Image:Feather.jpg|Feather.jpg]] by [[commons:User:Za|Za]] (''GFDL'', first Commons upload: 06:08, 29. Aug 2005)
{{GFDL}}</text>
    <sha1>3dcf291998d4711fd851b2b7ce46d0f8891d5c5f</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:M-en-sidebar.png</title>
  <ns>6</ns>
  <id>55</id>
  <revision>
    <id>172</id>
    <parentid>171</parentid>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">Screenshot of MediaWiki sidebar 
{{GPL}}</text>
    <sha1>54b8d72ab74ac9942a844c5bac9434eecb40a8e0</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:M-en-userlinks.png</title>
  <ns>6</ns>
  <id>56</id>
  <revision>
    <id>173</id>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">== Summary ==
Example user links screenshot for use in public domain help pages.

I grabbed this image and release it to the public domain, assuming that mediawiki does not impose any restrictions on screenshots.
== Licensing ==
{{PD}}</text>
    <sha1>6d6cd4828e7092e38d2d21b9cf6d88f69cb690de</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:M-en-pagetabs.png</title>
  <ns>6</ns>
  <id>57</id>
  <revision>
    <id>176</id>
    <parentid>175</parentid>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="235" xml:space="preserve">== Summary ==
Example page tabs screenshot for use in public domain help pages.

I grabbed this image and release it to the public domain, assuming that Mediawiki does not impose any restrictions on screenshots.

== Licensing ==
{{PD}}</text>
    <sha1>2bdda403a1ae9171486d3f70a67704e34fbd287d</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:M-en-interwiki lang.png</title>
  <ns>6</ns>
  <id>58</id>
  <revision>
    <id>177</id>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">== Summary ==
Screenshot of MediaWiki sidebar "other languages"

== Licensing ==
{{PD}}</text>
    <sha1>5456c5c1661b74d9c880a82a6f56fbc2cc34ad3c</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:M-en-recentchanges.png</title>
  <ns>6</ns>
  <id>59</id>
  <revision>
    <id>179</id>
    <timestamp>2008-07-29T18:30:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>1 revision</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">== Licensing ==
{{PD}}</text>
    <sha1>f8d945d6bc7a310c6f9b9b5b3ba2ae482655baa1</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>96940011</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>189</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T19:55:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Stock 96940011 image: [[Image:96940011.HEX]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">Stock 96940011 image: [[Image:96940011.HEX]]</text>
    <sha1>018b98b711570e772b994fd91de86d2d85fcb2d4</sha1>
  </revision>
  <revision>
    <id>186</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T19:58:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Some background, and a note about 96530006.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">96940011 was the original ROM on 2005 USDM MitsubishiEvolution vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]</text>
    <sha1>ffcc542bd976d1bbdfc2b63ffa2792ac6375410c</sha1>
  </revision>
  <revision>
    <id>182</id>
    <parentid>181</parentid>
    <timestamp>2008-07-29T20:20:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="337" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]</text>
    <sha1>097ab9fab721dbcc85d80e0cd630220e7d588eac</sha1>
  </revision>
  <revision>
    <id>188</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T21:23:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[96940011]] moved to [[ROMs:96940011]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="337" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]</text>
    <sha1>097ab9fab721dbcc85d80e0cd630220e7d588eac</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>28</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T19:55:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* 05 USDM VIII (96940011) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8584" xml:space="preserve">The [[Mitsubishi Lancer Evolution]] has a powerful stock [[Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [http://openecu.org/index.php?title=EcuFlash EcuFlash]

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec
==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===

===05 EDM VIII (96530006) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>043a676577ed25eae6e1e3ef9d086842bde3d1cd</sha1>
  </revision>
  <revision>
    <id>45</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:26:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8587" xml:space="preserve">The [[Mitsubishi Lancer Evolution]] has a powerful stock [[Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [http://openecu.org/index.php?title=EcuFlash EcuFlash]

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec
==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>a09ae1063bd4a01a2b0b2470d5d71d4f023d7354</sha1>
  </revision>
  <revision>
    <id>46</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:26:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8607" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [http://openecu.org/index.php?title=EcuFlash EcuFlash]

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec
==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>b94270b0c543357c32a7677ab65551ad09c63e3a</sha1>
  </revision>
  <revision>
    <id>25</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:50:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Tuning */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8567" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

=== General Tuing tutorial===
http://forums.evolutionm.net/showthread.php?t=201146&amp;highlight=maf+scaling
http://forums.evolutionm.net/showthread.php?t=302895
===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>00eb0641fea51e574ba6f452314d6df9185fc7ec</sha1>
  </revision>
  <revision>
    <id>2</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:52:17Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* General Tuing tutorial */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8607" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

=== General Tuning tutorial===

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]

===MAF Scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=249388&amp;highlight=maf+scaling
===Injector scaling tutorial===
http://forums.evolutionm.net/showthread.php?t=207924&amp;highlight=maf+scaling
===MIVEC Tuning===
http://forums.evolutionm.net/showthread.php?t=210569&amp;highlight=mivec

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>edcf99765a17de94f201b74320c1937ead4fa66b</sha1>
  </revision>
  <revision>
    <id>24</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:54:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Tuning */  Link updates and more informative descriptions.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8536" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
Tephra – a member of EvoM hailing from Melbourne Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features

- 2 levels of knock cel flash
- some ICS mods
- map switching (timing/fuel/boost)
- no lift to shift
- valet mode
- rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>f3bd13eeba0bed92c5b169fcfdecebd53a67765f</sha1>
  </revision>
  <revision>
    <id>23</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T20:55:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Tephra Mods */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8595" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>bdf936500ea8be108385e79bbc0c3b365f010852</sha1>
  </revision>
  <revision>
    <id>21</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:10:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Cold start enrichment */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9100" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.
===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]


==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>3320592892e5bd9bd58ff6709c02f6ea8ee7c436</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>File:96530006.HEX</title>
  <ns>6</ns>
  <id>61</id>
  <revision>
    <id>191</id>
    <timestamp>2008-07-29T20:24:43Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>2005 EDM Mitsubishi Lancer Evolution ROM image</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">2005 EDM Mitsubishi Lancer Evolution ROM image</text>
    <sha1>e4a308fc6aac945331c1616cf9f259366bee6d47</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>96530006</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>217</id>
    <parentid>214</parentid>
    <timestamp>2008-07-29T20:25:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: 96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.  Download: [[Image:96530006.HEX]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

Download: [[Image:96530006.HEX]]</text>
    <sha1>0d520a54dfc75b9855ccb4480bd23f080408b72a</sha1>
  </revision>
  <revision>
    <id>204</id>
    <parentid>199</parentid>
    <timestamp>2008-07-29T21:24:15Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[96530006]] moved to [[ROMs:96530006]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

Download: [[Image:96530006.HEX]]</text>
    <sha1>0d520a54dfc75b9855ccb4480bd23f080408b72a</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Helpful Links</title>
  <ns>0</ns>
  <id>63</id>
  <revision>
    <id>221</id>
    <parentid>219</parentid>
    <timestamp>2008-07-29T20:31:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: A few helpful links to other websites:  * [http://www.openecu.org/ OpenECU.org], home of [[EcuFlash]]. * [http://forums.evolutionm.net/forumdisplay.php?f=179 EvoM EcuFlash forum], a good p...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="325" xml:space="preserve">A few helpful links to other websites:

* [http://www.openecu.org/ OpenECU.org], home of [[EcuFlash]].
* [http://forums.evolutionm.net/forumdisplay.php?f=179 EvoM EcuFlash forum], a good place to start when looking for help.
* [http://www.aktivematrix.com/ ActiveMatrix], where more advanced technical discussion takes place.</text>
    <sha1>ed7af5352f8c41642c0be9be04f0e127fd4968cc</sha1>
  </revision>
  <revision>
    <id>220</id>
    <parentid>219</parentid>
    <timestamp>2008-07-29T20:40:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="414" xml:space="preserve">A few helpful links to other websites:

* [http://www.openecu.org/ OpenECU.org], home of [[EcuFlash]].
* [http://forums.evolutionm.net/forumdisplay.php?f=179 EvoM EcuFlash forum], a good place to start when looking for help.
* [http://www.aktivematrix.com/ ActiveMatrix], where more advanced technical discussion takes place.
* [http://www.limitless.co.nz/ EvoScan], a commonly-used commercial datalogging package.</text>
    <sha1>b21d517de092a17a024336e240b6382c1162945b</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>64</id>
  <revision>
    <id>230</id>
    <parentid>229</parentid>
    <timestamp>2008-07-29T20:31:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: * navigation ** mainpage|mainpage ** portal-url|portal ** currentevents-url|currentevents ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help ** helpfullinks|h...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** helpfullinks|helpfullinks</text>
    <sha1>f83a39ff3b024c7b2c8617b0ca0c1204b974bbc2</sha1>
  </revision>
  <revision>
    <id>224</id>
    <parentid>223</parentid>
    <timestamp>2008-07-29T20:31:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** helpful-links|helpful-links</text>
    <sha1>217d5d7650f8a9fccf5f1b1d35b4c6034e412c05</sha1>
  </revision>
  <revision>
    <id>225</id>
    <parentid>223</parentid>
    <timestamp>2008-07-29T20:31:57Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** helpful_links|helpful_links</text>
    <sha1>e4cbad2b9fa531123a80444e978bb34fbe2b42ce</sha1>
  </revision>
  <revision>
    <id>226</id>
    <parentid>223</parentid>
    <timestamp>2008-07-29T20:32:17Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** HelpfulLinks|HelpfulLinks</text>
    <sha1>42b32af646e262adfce2b944f3ab39f80967c9d3</sha1>
  </revision>
  <revision>
    <id>227</id>
    <parentid>223</parentid>
    <timestamp>2008-07-29T20:32:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="201" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** Helpful_Links|Helpful Links</text>
    <sha1>d6bed7917df55c474d32d871c2b9a86b417ff4c6</sha1>
  </revision>
  <revision>
    <id>228</id>
    <parentid>223</parentid>
    <timestamp>2008-07-29T20:34:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** support-url|support
** Helpful_Links|Helpful Links</text>
    <sha1>da4093ca1fd3740f4dedad3e7c3a9a461543d979</sha1>
  </revision>
  <revision>
    <id>222</id>
    <timestamp>2008-07-29T20:37:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="189" xml:space="preserve">* navigation
** mainpage|mainpage
** portal-url|portal
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** links-url|links</text>
    <sha1>ee712e6ac3243724ace1b9198c25a488fda3657d</sha1>
  </revision>
  <revision>
    <id>223</id>
    <parentid>222</parentid>
    <timestamp>2008-07-29T20:38:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="168" xml:space="preserve">* navigation
** mainpage|mainpage
** links-url|links
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help</text>
    <sha1>cccc3dbaecdf65c7592dd3db2f6a7a73cfb0c38b</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>MediaWiki:Links-url</title>
  <ns>8</ns>
  <id>65</id>
  <revision>
    <id>233</id>
    <parentid>232</parentid>
    <timestamp>2008-07-29T20:37:18Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Project:Links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">Project:Links</text>
    <sha1>c10ba1233eb215df3ccd636ec82ddce74f988de3</sha1>
  </revision>
  <revision>
    <id>234</id>
    <parentid>232</parentid>
    <timestamp>2008-07-29T20:37:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">Helpful_Links</text>
    <sha1>2154db8952b674280fc5d96a2e8b8a8d84b0c078</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>MediaWiki:Links</title>
  <ns>8</ns>
  <id>66</id>
  <revision>
    <id>236</id>
    <parentid>235</parentid>
    <timestamp>2008-07-29T20:38:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Helpful Links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">Helpful Links</text>
    <sha1>178674ddef1d1ceced9b221f91dff91c0e5b301a</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>EcuFlash</title>
  <ns>0</ns>
  <id>67</id>
  <revision>
    <id>246</id>
    <parentid>243</parentid>
    <timestamp>2008-07-29T20:44:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: [[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an ever-growing list of vehicles. EcuFlash uses the OpenPort vehicle interface to reflash v...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="587" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an ever-growing list of vehicles. EcuFlash uses the OpenPort vehicle interface to reflash vehicles via the OBDII port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a XML-based definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited. Future plans for EcuFlash include logging support / overlay, and live tuning.

See the OpenECU website[http://www.openecu.org/] for details.</text>
    <sha1>9b075144fc1184d54738aa201d3223d172071737</sha1>
  </revision>
  <revision>
    <id>240</id>
    <parentid>239</parentid>
    <timestamp>2008-07-29T20:50:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="698" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited. Future plans for EcuFlash include logging support / overlay, and live tuning.

See the [http://www.openecu.org/ OpenECU website] for details.</text>
    <sha1>1a28727c05cf7263508d4b6551482b5f93c77ed6</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>EvolutionM</title>
  <ns>0</ns>
  <id>68</id>
  <revision>
    <id>247</id>
    <timestamp>2008-07-29T20:56:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: [http://www.evolutionm.net/ EvolutionM] is a website and forum dedicated to [[wikipedia:Mitsubishi Lancer Evolution|Evo]] enthusiasts.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">[http://www.evolutionm.net/ EvolutionM] is a website and forum dedicated to [[wikipedia:Mitsubishi Lancer Evolution|Evo]] enthusiasts.</text>
    <sha1>2721291080eb939a6f90e54f89b20475d3471900</sha1>
  </revision>
</page>
<page arvcontinue="20080729183039|141">
  <title>Category:ROMs</title>
  <ns>14</ns>
  <id>69</id>
  <revision>
    <id>249</id>
    <parentid>248</parentid>
    <timestamp>2008-07-29T21:27:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: {{ROMs/Categories}}</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">{{ROMs/Categories}}</text>
    <sha1>6b97202353d405670599e0577bb9a1ef9ee69892</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Category:ROMs</title>
  <ns>14</ns>
  <id>69</id>
  <revision>
    <id>248</id>
    <timestamp>2008-07-29T21:27:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Removing all content from page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>96940011</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>187</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T21:28:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="355" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]
[[Category:ROMs]]</text>
    <sha1>1172def54646096afc2ee36a567c09875a14a7ad</sha1>
  </revision>
  <revision>
    <id>185</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T21:33:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="359" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]
[[Category:ROMs|694]]</text>
    <sha1>ace072695eece122ee1328cc7e2ff76e62102285</sha1>
  </revision>
  <revision>
    <id>183</id>
    <parentid>181</parentid>
    <timestamp>2008-07-29T21:33:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

Download: [[Image:96940011.HEX]]
[[Category:ROMs|96940011]]</text>
    <sha1>1aff7446784bf916a812c0d6200777ac2c5cf10a</sha1>
  </revision>
  <revision>
    <id>181</id>
    <timestamp>2008-07-29T21:36:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="410" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

==Download==
[[Image:96940011.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;3f314&lt;/tt&gt;
[[Category:ROMs|96940011]]</text>
    <sha1>ea212b90dffa43e6dd6562be855f7969a7ef2220</sha1>
  </revision>
  <revision>
    <id>184</id>
    <parentid>181</parentid>
    <timestamp>2008-07-29T21:47:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Addresses */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="647" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

==Download==
[[Image:96940011.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;3f314&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;899A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;899B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8976&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8977&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89F6&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89F7&lt;/tt&gt;

[[Category:ROMs|96940011]]</text>
    <sha1>cf19f3acba7ee07c4a30fbb3de8029b9855c25e1</sha1>
  </revision>
  <revision>
    <id>190</id>
    <parentid>184</parentid>
    <timestamp>2008-07-29T22:15:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[ROMs:96940011]] moved to [[96940011]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="647" xml:space="preserve">96940011 was the original ROM on 2005 USDM [[Wikipedia:Mitsubishi Lancer Evolution]] vehicles.

It has the unique property of being almost totally full of both code and tables, with very little room for additional patches. For additional functionality, users generally reflash with [[96530006]] instead.

==Download==
[[Image:96940011.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;3f314&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;899A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;899B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8976&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8977&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89F6&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89F7&lt;/tt&gt;

[[Category:ROMs|96940011]]</text>
    <sha1>cf19f3acba7ee07c4a30fbb3de8029b9855c25e1</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>96530006</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>206</id>
    <parentid>199</parentid>
    <timestamp>2008-07-29T21:29:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="173" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

Download: [[Image:96530006.HEX]]
[[Category:ROMs]]</text>
    <sha1>c3028b49c6e897b70bd3279d9a8939fecf7e40a5</sha1>
  </revision>
  <revision>
    <id>203</id>
    <parentid>199</parentid>
    <timestamp>2008-07-29T21:30:26Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="177" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

Download: [[Image:96530006.HEX]]
[[Category:ROMs|653]]</text>
    <sha1>ba0d650de70ebf4f21d8596f79a4557cf3618423</sha1>
  </revision>
  <revision>
    <id>201</id>
    <parentid>199</parentid>
    <timestamp>2008-07-29T21:35:57Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="219" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

==Download==
[[Image:96530006.HEX]]

==Addresses==

;MUT Table
:36200
[[Category:ROMs|96530006]]</text>
    <sha1>64c1c5089fc4df089263d6979688e40d429879e0</sha1>
  </revision>
  <revision>
    <id>200</id>
    <parentid>199</parentid>
    <timestamp>2008-07-29T21:36:32Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="228" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

==Download==
[[Image:96530006.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>d5cefadf038cc83994326c400b81cf4ec8cf7154</sha1>
  </revision>
  <revision>
    <id>197</id>
    <parentid>192</parentid>
    <timestamp>2008-07-29T21:46:45Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="464" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

==Download==
[[Image:96530006.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>8c7ae47d241bca121bb0da0b928e72ac33f04559</sha1>
  </revision>
  <revision>
    <id>195</id>
    <parentid>192</parentid>
    <timestamp>2008-07-29T22:15:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[ROMs:96530006]] moved to [[96530006]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="464" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

==Download==
[[Image:96530006.HEX]]

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>8c7ae47d241bca121bb0da0b928e72ac33f04559</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>20</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:31:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9216" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====
http://forums.evolutionm.net/showthread.php?t=337811

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>117fd3ff8df07a1138e23c6d722780aaee819485</sha1>
  </revision>
  <revision>
    <id>19</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:42:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* MUT tables */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9438" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====

* [[AddMutTableToEcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====2-byte data logging====
http://forums.evolutionm.net/showthread.php?t=327185&amp;highlight=byte+load

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>3d387a3e2161f8c3e1919969a5f60bd31cae2d5b</sha1>
  </revision>
  <revision>
    <id>18</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:42:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* 2-byte data logging */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9338" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT tables====

* [[AddMutTableToEcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]


====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>90c1a0d25f06a0fdbfe161f51e30d81f7b1b3948</sha1>
  </revision>
  <revision>
    <id>16</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:43:15Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* MUT tables */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9340" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT and 2-Byte====

* [[AddMutTableToEcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>efb32dc2cc8a3da5270d75cfabedd451c0e25970</sha1>
  </revision>
  <revision>
    <id>15</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:44:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* MUT and 2-Byte */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9344" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load


===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>3575dc60b74af56c5789886f85bc647491632654</sha1>
  </revision>
  <revision>
    <id>14</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T21:44:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Lean Spool */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9343" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>d80a9942a39c50e775d8e52dd314657beb8d613e</sha1>
  </revision>
  <revision>
    <id>13</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T22:11:20Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* MUT and 2-Byte */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9419" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

====2-Byte Logging====
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[ROMs:96940011]])===
===05 EDM VIII ([[ROMs:96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>9c622eae581240b1334dcdc95d1ce11fb02da4a6</sha1>
  </revision>
  <revision>
    <id>12</id>
    <parentid>1</parentid>
    <timestamp>2008-07-29T22:15:54Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Download Section */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9409" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Enrichment_Tables.jpeg]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

====2-Byte Logging====
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>79be6e2997ed31c3fb7f743657a3355a30ae4ec4</sha1>
  </revision>
  <revision>
    <id>10</id>
    <parentid>1</parentid>
    <timestamp>2008-07-30T01:03:54Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Cold start enrichment */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9407" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Startup_IPW_data.gif]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

====2-Byte Logging====
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
http://forums.evolutionm.net/showthread.php?t=261465&amp;highlight=byte+load

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>056c762b2aa21b90c2b2501f181f2722bf5f909d</sha1>
  </revision>
  <revision>
    <id>9</id>
    <parentid>1</parentid>
    <timestamp>2008-07-30T01:32:54Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Lean Spool */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9420" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This article will detail how to tune, patch, and log your stock ECU.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Startup_IPW_data.gif]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

====2-Byte Logging====
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
* [http://forums.evolutionm.net/showthread.php?t=261465 Disable lean spool on Evo IX]

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>ddede7fe2952800fe607fa8c357da729dab4d050</sha1>
  </revision>
  <revision>
    <id>8</id>
    <parentid>1</parentid>
    <timestamp>2008-07-30T12:34:45Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9612" xml:space="preserve">The [[Wikipedia:Mitsubishi Lancer Evolution]] has a powerful stock [[Wikipedia:Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

==Warning==
Tuning or patching the ECU can be '''VERY DANGERIOUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Tuning==
ECU tuning for the Evo is accomplished with the use of [[EcuFlash]].

* [http://forums.evolutionm.net/showthread.php?t=201146 ECUflash tutorial for beginners]
* [http://forums.evolutionm.net/showthread.php?t=302895 How To Tune An Evo]
* [http://forums.evolutionm.net/showthread.php?t=249388 How to scale your MAF]
* [http://forums.evolutionm.net/showthread.php?t=207924 Injector scaling and latency for different injectors]
* [http://forums.evolutionm.net/showthread.php?t=210569 MIVEC tuning]

==Patching==
Patching is new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

===Individual ROMs===
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

===Tephra Mods===
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  His latest roms includes the following features:

* 2 levels of knock cel flash
* some ICS mods
* map switching (timing/fuel/boost)
* no lift to shift
* valet mode
* rear o2 simulator (not heater)

===Misc Mods===
====Removing pin from Evo IX ECU====
http://forums.evolutionm.net/showthread.php?t=337811
====AIT logging through ECU====
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

====Cold start enrichment====
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

[[Image:Startup_IPW_data.gif]]

====MUT and 2-Byte====

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

====2-Byte Logging====
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

====Lean Spool====
* [http://forums.evolutionm.net/showthread.php?t=261465 Disable lean spool on Evo IX]

===Boost Control Mods===
====Log boost with JDM MAP sensor====
http://forums.evolutionm.net/showthread.php?t=259595

====Improved load based boost control====
http://forums.evolutionm.net/showthread.php?t=288408

====Direct Boost Control (PSI)====
Originally discovered [http://forums.evolutionm.net/showthread.php?t=293981&amp;highlight=boost here]

====Additional boost tables====
http://forums.evolutionm.net/showthread.php?t=333479

===02 Sensor Mods===
====Log wideband AFR through ECU(rear 02 sim)====
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

====Front &amp; rear 02 sim (control closed loop with wideband)====
http://forums.evolutionm.net/showthread.php?t=360398

==Logging==
ECU logging for the Evo is accomplished with the use of [http://www.limitless.co.nz/ EvoScan] or [http://www.aktivematrix.com/forum/dload.php?action=category&amp;cat_id=13 MitsuLogger]

==Download Section==
===03-05 JDM VIII (96260009)===
===03-05 JDM RA (90550001)===
===03-04 USDM VIII (94170015)===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX (88590015)===
Tepha Mod v5.8, Lean Spool Disable, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

Tepha Mod v5.8, JDM Map sensor, Lean Spool Disable, Direct Boost Control, Rear 02 Sim, AIT logging, (download link here containing rom, EcuFlash XML, and Evoscan Data Settings)

===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>91e1aac430612114e812d2ec1794a9e5940527de</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Add MUT Table To EcuFlash</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>257</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T21:40:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: * Locate your ROM ID (an 8-digit number, something like [[96940011]]).  * Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table addr...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2444" xml:space="preserve">* Locate your ROM ID (an 8-digit number, something like [[96940011]]).

* Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.

* Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.

* In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.

* Add the following chunk of XML to the very end of the file, making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)

&lt;pre&gt;
&lt;table name="MUT table" category="MUT" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;</text>
    <sha1>54e1139b0d7ead76c1ff05aab12c94c172f5e898</sha1>
  </revision>
  <revision>
    <id>250</id>
    <timestamp>2008-07-29T21:43:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>[[AddMutTableToEcuFlash]] moved to [[Add MUT Table To EcuFlash]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2444" xml:space="preserve">* Locate your ROM ID (an 8-digit number, something like [[96940011]]).

* Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.

* Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.

* In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.

* Add the following chunk of XML to the very end of the file, making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)

&lt;pre&gt;
&lt;table name="MUT table" category="MUT" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;</text>
    <sha1>54e1139b0d7ead76c1ff05aab12c94c172f5e898</sha1>
  </revision>
  <revision>
    <id>256</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T21:51:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2500" xml:space="preserve">* Locate your ROM ID (an 8-digit number, something like [[96940011]]).

* Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.

* Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.

* In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.

* Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)

&lt;pre&gt;
&lt;table name="MUT table" category="MUT" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;</text>
    <sha1>32a48b1d7d87e0c2220bc029d71ee72705417df1</sha1>
  </revision>
  <revision>
    <id>255</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T21:53:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2692" xml:space="preserve"># Locate your ROM ID (an 8-digit number, something like [[96940011]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.
# Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.
# In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.
# Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)

&lt;pre&gt;
&lt;table name="MUT table" category="MUT" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>6a5ef10a75e262fa2a93a1b6be14aad4df9d60a9</sha1>
  </revision>
  <revision>
    <id>254</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T21:59:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2983" xml:space="preserve"># Locate your ROM ID (an 8-digit number, something like [[96940011]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.
# Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.
# In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.
# Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)
# Open the HEX or BIN file for your ROM with [[EcuFlash]].
# Scroll down to the "Misc" section, and you should see "MUT Table". Open it, and confirm that it is reading correctly; you should see a large 16x32-element table, with alternating rows of data and &lt;tt&gt;FFFF&lt;/tt&gt;.

===XML to add:===
&lt;pre&gt;
&lt;table name="MUT table" category="Misc" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>794134e0f159cd0ca9b082bcb488bfd1658a1c29</sha1>
  </revision>
  <revision>
    <id>253</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T22:02:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3040" xml:space="preserve"># Locate your ROM ID (an 8-digit number, something like [[96940011]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.
# Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.
# In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.
# Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)
# Open the HEX or BIN file for your ROM with [[EcuFlash]].
# Scroll down to the "Misc" section, and you should see "MUT Table". Open it, and confirm that it is reading correctly; you should see a large 16x32-element table, with alternating rows of data and &lt;tt&gt;FFFF&lt;/tt&gt;.

===What it should look like:===
[[Image:Mut-table.png]]

===XML to add:===
&lt;pre&gt;
&lt;table name="MUT table" category="Misc" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>d5a70e403d0eca2d42862a42ed2c82c133a94366</sha1>
  </revision>
  <revision>
    <id>252</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T22:03:10Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* What it should look like: */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3034" xml:space="preserve"># Locate your ROM ID (an 8-digit number, something like [[96940011]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.
# Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.
# In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.
# Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)
# Open the HEX or BIN file for your ROM with [[EcuFlash]].
# Scroll down to the "Misc" section, and you should see "MUT Table". Open it, and confirm that it is reading correctly; you should see a large 16x32-element table, with alternating rows of data and &lt;tt&gt;FFFF&lt;/tt&gt;.

===What it looks like:===
[[Image:Mut-table.png]]

===XML to add:===
&lt;pre&gt;
&lt;table name="MUT table" category="Misc" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>289846690f0723aea7574e62dcec7d3c6c6bb553</sha1>
  </revision>
  <revision>
    <id>258</id>
    <parentid>251</parentid>
    <timestamp>2008-07-29T23:13:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3053" xml:space="preserve"># Locate your ROM ID (an 8-digit number, something like [[96940011]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the MUT table address.
# Open up the directory &lt;tt&gt;C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo&lt;/tt&gt;.
# In that directory, find a file named &lt;tt&gt;'''romid.xml'''&lt;/tt&gt; (ie. &lt;tt&gt;96940011.xml&lt;/tt&gt;). Open that file with notepad or wordpad.
# Add the following chunk of XML to the very end of the file (but before the "&lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;" text at the very end), making sure to change the &lt;tt&gt;address="XXX"&lt;/tt&gt; portion on the first line to refer to the MUT table address for your ROM. (For example, if your ROM is [[96940011]], then your MUT table address is &lt;tt&gt;3f314&lt;/tt&gt;, so you would change that section to &lt;tt&gt;address="3f314"&lt;/tt&gt;.)
# Open the HEX or BIN file for your ROM with [[EcuFlash]].
# Scroll down to the "Misc" section, and you should see "MUT Table". Open it, and confirm that it is reading correctly; you should see a large 16x32-element table, with alternating rows of data and &lt;tt&gt;FFFF&lt;/tt&gt;.

===What it looks like:===
[[Image:Mut-table.png|center|thumb|600px]]

===XML to add:===
&lt;pre&gt;
&lt;table name="MUT table" category="Misc" address="XXX" type="3D" level="1" scaling="Hex16"&gt;
    &lt;table name="X" type="Static X Axis" elements="32" scaling="Hex16"&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;0&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;1&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;2&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;3&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;4&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;5&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;6&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;7&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;8&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;9&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;A&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;B&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;C&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;D&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;E&lt;/data&gt;
        &lt;data&gt;-&lt;/data&gt;&lt;data&gt;F&lt;/data&gt;
    &lt;/table&gt;
    &lt;table name="Y" type="Static Y Axis" elements="30"&gt;
        &lt;data&gt;MUT0X&lt;/data&gt;
        &lt;data&gt;MUT1X&lt;/data&gt;
        &lt;data&gt;MUT2X&lt;/data&gt;
        &lt;data&gt;MUT3X&lt;/data&gt;
        &lt;data&gt;MUT4X&lt;/data&gt;
        &lt;data&gt;MUT5X&lt;/data&gt;
        &lt;data&gt;MUT6X&lt;/data&gt;
        &lt;data&gt;MUT7X&lt;/data&gt;
        &lt;data&gt;MUT8X&lt;/data&gt;
        &lt;data&gt;MUT9X&lt;/data&gt;
        &lt;data&gt;MUTAX&lt;/data&gt;
        &lt;data&gt;MUTBX&lt;/data&gt;
        &lt;data&gt;MUTCX&lt;/data&gt;
        &lt;data&gt;MUTDX&lt;/data&gt;
        &lt;data&gt;MUTEX&lt;/data&gt;
        &lt;data&gt;MUTFX&lt;/data&gt;
        &lt;data&gt;MUT10X&lt;/data&gt;
        &lt;data&gt;MUT11X&lt;/data&gt;
        &lt;data&gt;MUT12X&lt;/data&gt;
        &lt;data&gt;MUT13X&lt;/data&gt;
        &lt;data&gt;MUT14X&lt;/data&gt;
        &lt;data&gt;MUT15X&lt;/data&gt;
        &lt;data&gt;MUT16X&lt;/data&gt;
        &lt;data&gt;MUT17X&lt;/data&gt;
        &lt;data&gt;MUT18X&lt;/data&gt;
        &lt;data&gt;MUT19X&lt;/data&gt;
        &lt;data&gt;MUT1AX&lt;/data&gt;
        &lt;data&gt;MUT1BX&lt;/data&gt;
        &lt;data&gt;MUT1CX&lt;/data&gt;
        &lt;data&gt;MUT1DX&lt;/data&gt;
    &lt;/table&gt;
&lt;/table&gt;
&lt;/pre&gt;

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>955b0e05d1106c837195592d39e13d1afcbfc302</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>AddMutTableToEcuFlash</title>
  <ns>0</ns>
  <id>71</id>
  <revision>
    <id>259</id>
    <timestamp>2008-07-29T21:43:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>[[AddMutTableToEcuFlash]] moved to [[Add MUT Table To EcuFlash]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39" xml:space="preserve">#REDIRECT [[Add MUT Table To EcuFlash]]</text>
    <sha1>5e884eedaae87b8516d998cd743cbae4439fa54d</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>File:Mut-table.png</title>
  <ns>6</ns>
  <id>72</id>
  <revision>
    <id>260</id>
    <timestamp>2008-07-29T22:02:00Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>EcuFlash representation of the Evo MUT table</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">EcuFlash representation of the Evo MUT table</text>
    <sha1>e13255e33bc96cc4474900a39faccfbbce5a7816</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>2-Byte Logging</title>
  <ns>0</ns>
  <id>73</id>
  <revision>
    <id>261</id>
    <timestamp>2008-07-29T22:11:13Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: # Edit the [[EcuFlash]] XML for [[:Category:ROMs|your rom]] to add the MUT table ([[Add_MUT_Table_To_EcuFlash|instructions]]). # Find the documentation specific to your ROM in our [[:Categ...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="960" xml:space="preserve"># Edit the [[EcuFlash]] XML for [[:Category:ROMs|your rom]] to add the MUT table ([[Add_MUT_Table_To_EcuFlash|instructions]]).
# Find the documentation specific to your ROM in our [[:Category:ROMs|master index]], and look up the 2-byte load, RPM, and airflow addresses.
# Open up your ROM in EcuFlash, and open the MUT table (in the "Misc" section).
# Find the MUT chart locations for the 2-byte load, RPM, and airflow for your ROM, and enter the new addresses. For example, if your ROM is [[96940011]], change the value in the &lt;tt&gt;MUT0&lt;/tt&gt; row and &lt;tt&gt;0&lt;/tt&gt; column to &lt;tt&gt;899A&lt;/tt&gt; and the &lt;tt&gt;1&lt;/tt&gt; column to &lt;tt&gt;899B&lt;/tt&gt; to add 2-byte load. Do the same for RPM and for airflow.
# When logging in [[EvoScan]], you can now enable 2-byte load, RPM and airflow!

Credit goes to [http://forums.evolutionm.net/member.php?u=68675 Jack_of_Trades] for his [http://forums.evolutionm.net/showthread.php?t=327185 original thread] on [[EvolutionM]] documenting this.</text>
    <sha1>7405b6e1f9f434fcd9153993e306c4f580e546b9</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>ROMs:96940011</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>263</id>
    <timestamp>2008-07-29T22:15:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>[[ROMs:96940011]] moved to [[96940011]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">#REDIRECT [[96940011]]</text>
    <sha1>ada8fe93375b037e1a2818c00b4773fdc4a08a1d</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>ROMs:96530006</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>264</id>
    <timestamp>2008-07-29T22:15:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>[[ROMs:96530006]] moved to [[96530006]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">#REDIRECT [[96530006]]</text>
    <sha1>9e768e0af80a393b2df4b39f468cfa40a08c67f6</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Talk:2-Byte Logging</title>
  <ns>1</ns>
  <id>76</id>
  <revision>
    <id>265</id>
    <timestamp>2008-07-29T22:16:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: TODO: need to add information about logging 2-byte MUT entries for older versions of [[EvoScan]] and [[MitsuLogger]].</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="117" xml:space="preserve">TODO: need to add information about logging 2-byte MUT entries for older versions of [[EvoScan]] and [[MitsuLogger]].</text>
    <sha1>7808915a2370aedac6b2cd629be8572cf4a33e4d</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Talk:94170015</title>
  <ns>1</ns>
  <id>80</id>
  <revision>
    <id>276</id>
    <timestamp>2008-08-01T11:30:00Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Was 94170015 (or earlier versions) actually shipped on 2005 models? I was under the impression that the US market only received [[96940011]] for 2005 model year vehicles. --~~~~</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="229" xml:space="preserve">Was 94170015 (or earlier versions) actually shipped on 2005 models? I was under the impression that the US market only received [[96940011]] for 2005 model year vehicles. --[[User:EdwardMarshall|logic]] 06:30, 1 August 2008 (CDT)</text>
    <sha1>2602f18d44c4c9cc95a45f2ce934be18ab2ddcd3</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>How to Tune an Evo TB Alternate</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>460</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:09:09Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* TB's guide to tuning with ECUFlash */  Convert to Wiki format, get rid of HTML.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44708" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
&lt;br&gt;
== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== &lt;b&gt;&lt;font color="DarkOrange"&gt;What you'll need&lt;/font&gt;&lt;/b&gt; ==
Before you get started, you'll need a few basics. Some of thesenecessities are going to lighten your pocket a little, but you drive anEvo ... you can afford it, right?
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Tuning Software:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. Thisis open source software and a free download.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Logging Software:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is thesoftware I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan issimple and easy to use. It also works with most of the wideband O2sensors you'll find.
&lt;br&gt;

&lt;br&gt;
[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) byMalibuJack, who you might know from EvoM. He knows his stuff, and hislogger reflects that. It's powerful and constantly being updated. Ifyou have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him onhis own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM inthe [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].
&lt;br&gt;

&lt;br&gt;
[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed byInnovate Motorsports and is packaged with many of their products. Ihave this software, but I honestly haven't used it much. I hear thatit's a smart, fast logger that can do anything you want and more afteryou learn how to use it. Lots of tuners love this software and wouldn'ttrade it for the world.
&lt;br&gt;

&lt;br&gt;
Of course, these aren't the only choices for logging data from yourECU. Find a logger you like and learn your way around it. You can usethe information here with any logger you end up with.
&lt;br&gt;

&lt;br&gt;
And now, the hardware ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;OBDII Interface Cable:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. Thiscable is used when data is being sent to or being pulled from the ECU.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Boost Gauge:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
You need to monitor the boost carefully when tuning your car. A boostgauge is the absolute minimum you need. A better solution is to logboost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge thatMitsubishi left in the car for me.
&lt;br&gt;

&lt;br&gt;
Boost gauges are everywhere and range for super cheap to insanelyexpensive. Pick one and install it. If you want my opinion, I've hadVDO and Stewart Warner gauges and never had trouble with either.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Wideband (5v) O2 Sensorand Interface:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
I'll give a little explanation here. You have 2 O2 (oxygen) sensors onyour car from the factory. One is in the turbo outlet pipe, and theother is just past the catalytic converter. The first one tells the ECUinformation about the fuel mixture, and the second is used incomparison to the first to determine if the converter is doing its job.
&lt;br&gt;

&lt;br&gt;
Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technicallyisn't a problem and narrow band O2 sensors can be used to monitorair/fuel mixtures when tuning, but the stock sensors are calibrated insuch a way that they stop giving feedback at a certain load or throttlepercentage and the car enters "open loop" mode. This brings us to ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying onthe O2sensors to give it feedback on the car's air to fuel mixture.Basically, in open loop mode, the ECU aims for a set fuel mixture andjust kind of assumes that that mixture is correct based on the thingsit DOES know, such as the MAF reading.
&lt;br&gt;

&lt;br&gt;
So, in order to achieve the ideal fuel mixture, we need to know thespecifics of the fuel mixture when in open loop mode, especially sinceopen loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This isusually a "wideband" sensor that sends signals from 0.00v to 5.00v. Thehigher range of the sensor allows for more accurate readings.
&lt;br&gt;

&lt;br&gt;
Here are some common wideband O2 choices ...
&lt;br&gt;

&lt;br&gt;
[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentionedearlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.
&lt;br&gt;

&lt;br&gt;
[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setupover the LC-1 is the option of an LCD display panel and a controlmodule to interface with other sensors to monitor things such as boostpressure and exhaust gas temperatures. Innovate offers similar optionsif you upgrade to the LM-1 unit.
&lt;br&gt;

&lt;br&gt;
There are of course other options for wideband O2 sensors and most willbe supported by the logger you choose.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Optional Hardware:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Items listed here aren't required to properly tune your car, but alittle extra info never hurt anyone.
&lt;br&gt;

&lt;br&gt;
MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with therest of your log and could possibly allow you to catch subtle pressurenuances that you might not spot on the gauge.
&lt;br&gt;

&lt;br&gt;
On the Evo, there is a nifty way to log boost with a part from Japanand some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also manyaftermarket kits that allow you to log boost.
&lt;br&gt;

&lt;br&gt;
EGT Gauge - I've personally never dealt with one of these doo-dads, butmonitoring your EGT (Exhaust Gas Temperature) can keep you from makingsome big mistakes while tuning. If you want to go this route, you'llneed to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]
&lt;br&gt;

&lt;br&gt;
So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]
== &lt;b&gt;&lt;font color="DarkOrange"&gt;AAAHHHH&amp;#33; Lots of colors and numbers&amp;#33;&lt;/font&gt;&lt;/b&gt; ==
Alrighty, so you now have everything you need to get started. Let's getyou familiarized with the software you'll be working with.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;ECUFlash&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
ECUFlash is the application that you will use to write to and from yourECU. It comes packaged with everything you need to get started, minus aROM image from your car.
&lt;br&gt;

&lt;br&gt;
If you have your OBDII cable nearby, you can run out to your car andpull the image from it to use for this section. If you don't have acable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past thispart.
&lt;br&gt;

&lt;br&gt;
You know how to connect the OBDII cable to your car right? RIGHT? Whatdo you mean you didn't read the article I sent you to in the firstpost? Okay, fine&amp;#33; [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].
&lt;br&gt;

&lt;br&gt;
So, you're plugged in a ready to go, right? Good. Open up ECUFlash.you'll be greeted with this screen ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen01.gif]]
&lt;br&gt;

&lt;br&gt;
Now, take a second to get familiar with the buttons at the top of thescreen ...
&lt;br&gt;

&lt;br&gt;
[[Image:ecuFlashButtons.gif]]
&lt;br&gt;

&lt;br&gt;
Open ROM - This will open a saved ROM image for editing or flashing.
&lt;br&gt;
Save ROM As - This saves the edits you've made to the ROM.
&lt;br&gt;
Read From ECU - This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
&lt;br&gt;
Write to ECU - This writes the selected ROM file in ECUFlash to the ECU.
&lt;br&gt;
Test Write to ECU - The goes through the same processes as the "Writeto ECU" function, but no data is actually writted to the ECU.
&lt;br&gt;
Compare to ECU - This reads the image from the ECU and compares it tothe selected ROM image in ECUFlash. This process runs every time youwrite to the ECU, and only the modified ROM data is written to the ECU.
&lt;br&gt;

&lt;br&gt;
If you're connected to the ECU properly, the "Read from ECU" icon willbe lit. Go ahead and click the "Read from ECU" icon. You'll get thisprompt ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen02.gif]]
&lt;br&gt;

&lt;br&gt;
Select the vehicle that you are connected to and click "Read" to begintransferring your current ROM image to your computer. When the processhas finished, your screen should look similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen03.gif]]
&lt;br&gt;

&lt;br&gt;
On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and"Parameters" in the lower box. This would also be a good time to savethis ROM somewhere safe before you go poking around and changing stuff.Just click the "Save ROM As" button at the top and select a location.
&lt;br&gt;

&lt;br&gt;
(Those of you who used the ROM I linked to from above can tune back innow)
&lt;br&gt;

&lt;br&gt;
Before you start tuning, it's best that you know a little about theinformation contained in your ROM image, so I'll start there ...
&lt;br&gt;

&lt;br&gt;
The "&lt;b&gt;ROM Info&lt;/b&gt;" section contains, well, info aboutthe ROMyou're looking at. If you expand that section by clicking the little[+] to the left, you should see info that reflects the vehicle it waspulled from ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen04.gif]]
&lt;br&gt;

&lt;br&gt;
Most of the info here is self explanatory, but note the value of"Internal ID." This internal ID is often referred to as the "definitionfile." In the ROM pictured above, the definition is "88590015" andhappens to be the most common Evo IX ROM.
&lt;br&gt;

&lt;br&gt;
Now, below the ROM Info section is the good stuff ... the "&lt;b&gt;Parameters&lt;/b&gt;."These Parameters hold the data that controls the variables you willharness to fine tune the performance of your Evo. The categories withinare pretty cut and dry. They include:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The fuel category includes the ever importantfuel maps,as well as more advanced info such as the MAF and injector scalingtables.
&lt;br&gt;
&lt;b&gt;Timing&lt;/b&gt; - The timing category hold your ignition andMIVEC maps.
&lt;br&gt;
&lt;b&gt;Limits&lt;/b&gt; - Within the limits category you'll find therev limit, stationary rev limit (fun fun), and speed limit tables.
&lt;br&gt;
&lt;b&gt;Turbo&lt;/b&gt; - the turbo category holds a ton of importantinfo. Thetables here control the desired boost, wastegate duty, and overboostprotection. This is probably the most confusing section of them all.
&lt;br&gt;
&lt;b&gt;Misc&lt;/b&gt; - The most important data here is theimmobilizer table.You'll need to set your user level to "Developer" to see this though.This category is also commonly used to store any tables you add to theROM definition (we'll cover this later).
&lt;br&gt;
&lt;b&gt;Idle&lt;/b&gt; - These isn't much here, but the tables withincontrol your desired idle settings.
&lt;br&gt;

&lt;br&gt;
With that out of the way, we can start looking at maps. Yay&amp;#33;
&lt;br&gt;

&lt;br&gt;
There are 3 levels of maps in ECUFlash ...
&lt;br&gt;

&lt;br&gt;
1D - A 1D map contains one address and a value for that address.
&lt;br&gt;
2D - A 2D map contains a reference column of addresses and values foreach address in a second column.
&lt;br&gt;
3D - A 3D map cross references 2 address and assigns a value based ontheir relation.
&lt;br&gt;

&lt;br&gt;
Here are some examples of the different types of maps ...
&lt;br&gt;

&lt;br&gt;
1D
&lt;br&gt;
[[Image:revLimitMap.gif]]
&lt;br&gt;

&lt;br&gt;
2D
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;

&lt;br&gt;
3D
&lt;br&gt;
[[Image:fuelMap.gif]]
&lt;br&gt;

&lt;br&gt;
3D maps can also be viewed as 3D graphs, like this one ...
&lt;br&gt;
[[Image:3dMap.gif]]
&lt;br&gt;

&lt;br&gt;
Reading the 1D and 2D maps is pretty straight forward, but the 3D mapis a little more difficult. Basically, the ECU compares the 2stationary values on the X and Y axis then assigns the corresponding Zaxis value. Take a look at the illustrations below for more clarity ...
&lt;br&gt;

&lt;br&gt;
[[Image:3dTableExplained.jpg]]
&lt;br&gt;

&lt;br&gt;
In the fuel map illustration above, the ECU is reading an engine loadvalue of "180" and an RPM value of "5500." The cell where the 180 loadcolumn and 5500 RPM row intersect decides the AFR value, which is"10.1."
&lt;br&gt;

&lt;br&gt;
Now that you know how to read the maps, you need to know how to modifythem. It is actually pretty straight forward and simple ...
&lt;br&gt;

&lt;br&gt;
"=" pops up a dialog box and allows you to directly input a value in tothe seleted cell(s).
&lt;br&gt;
"+" incrementally increases the selected value(s).
&lt;br&gt;
"-" incrementally decreases the selected value(s).
&lt;br&gt;

&lt;br&gt;
You can also copy and paste values to and from the maps using thestandard Windows CTRL+C to copy and CTRL+V to paste. If you want toknow more, check out the "Edit" menu in an open map window.
&lt;br&gt;

&lt;br&gt;
Okay, well that about sums it up for the basics of using ECU flash. Nowit's time to find out what values we need to change and why ...
== &lt;b&gt;&lt;font color="DarkOrange"&gt;Pressure predicament&lt;/font&gt;&lt;/b&gt; ==
When I first started the tune for my car, I chose to begin with settingthe boost. The reason for this was to hopefully reduce the amounttuning needed later in the process.
&lt;br&gt;

&lt;br&gt;
By first setting the amount of air being shoved on to the cylinders, Icould finish the first half of the AFR tuning without even touching thefuel maps. More importantly, the boost tables are directly related tothe load values that the ECU uses as a basis reading values from mostall of the tables that you will be editing while building your tune. Bysetting the boost first, you dial in the load values that you will beediting in the steps afterward.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Ways to tune boostpressure&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There are basically two ways to set the boost levels on your Evo. Youcan install a boost controller, or modify the factory boost controlsystem. Both have their pros and cons ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Aftermarket BoostController&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The main benefit of the boost controller option is ease of use. Thisoption gives you direct, mechanical (or electronic) control of theboost level. Some options allow you to adjust the boost on-the-fly fromthe driver's seat, and that type of control is insanely convenient.
&lt;br&gt;

&lt;br&gt;
The downside of this option is mainly the amount of control you haveover the boost levels. Some of the more expensive electroniccontrollers allow you to customize the boost curve based on RPM, butyour basic manual controller does not. Also, by disabling the stockboost control system, you forfeit the ECU's overboost protection.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Modified Stock BoostControl System&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
With this option, you have tons of control over the boost dynamics. Youcan dial out spikes and reduce taper. The method also retains the ECU'sability to reduce boost pressure in situations that might harm yourengine. There is also a cost savings with this route.
&lt;br&gt;

&lt;br&gt;
Modifying the stock boost control system is also a little tedious andtime consuming. There are many tables that interact with each other tomake it all work, and when you start tinkering with the hardware thatthese values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash theECU which requires some time and a computer.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withan aftermarket boost controller&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
This is by far the easiest and fastest method to set the boost on yourEvo. You simply remove the stock boost control system and replace itwith an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boostcontroller], so I'll just send you there in stead of wastingtime reiterating it all.
&lt;br&gt;

&lt;br&gt;
Once you have your boost controller installed, be sure to adjust it allthe way down to avoid initial overboosting. Make some runs, preferablyin 4th gear, and monitor the boost levels. Turn the boost up in smallincrements until you reach your desired boost level. Read the loggingsection further down for more info.
&lt;br&gt;

&lt;br&gt;
A stock Evo IX can easily handle 22 psi after the needle settles. Aspike of 24 or 25 psi can be expected in the peak torque area. Theboost is likely to taper down toward redline, but it should still be animprovement over stock.
&lt;br&gt;

&lt;br&gt;
If you have choosen to install a manual boost controller, you'vebasically rendered the ECU's boost control features useless, but thereare a few tables you might want to change anyway. Increasing the valuesin the "Boost Limit" table may help keep the ECU from cutting fuel inan overboost situation.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withthe stock BCS&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Grab a seat, because things are about to get interesting ...
&lt;br&gt;

&lt;br&gt;
For starters, controlling boost using the factory boost control systemisn't 100% dependent on settings in the ECU. This is due to Mitsuinstalling handy restrictor pills in the OE boost control solenoid(BCS) lines. There is one pill just before the BCS on the pressure sideand one in the short line just before the turbo. Modifying either ofthese pills will change the boost characteristics. Wrcwannabe givessome great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learnmore.
&lt;br&gt;

&lt;br&gt;
For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify thestock boost control pill for any information I give you to beapplicable. Go ahead and read through that thread and head back overhere after you have an understanding of the mechanical side ofmodifying for ECU boost control.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Boost control tables&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Before we get too far in to this stuff, you might want to set your userlevel in ECUFlash to "Developer". To do this, select "Options" from themenu up top. You'll see a user level section on the left. Open that upand select "Developer" from the pull down menu. &lt;font color="Red"&gt;WARNING&lt;/font&gt;:Changing the user level opens up many other tables that we may or maynot be using in this tutorial. If you don't know what a table is, don'tmess with it. Setting values in ECUFlash incorrectly could possiblycause irreversible damage to your Evo.
&lt;br&gt;

&lt;br&gt;
On the Evo, there are no less than six tables that control boost. Thesetables are (in order of appearance):
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt;
&lt;br&gt;
[[Image:boostDelayTimerMap.gif]]
&lt;br&gt;
This map works with the "Boost Limit" map to protect the system fromoverboost. This map is a timer (in milliseconds) that comes in to playwhen your actual boost at a given RPM exceeds the value set in the"Boost Limit" table. If boost exceeds the limit for a time greater thanthe timer's value, the wastegate is opened to lower boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Control Load Offset&lt;/b&gt;
&lt;br&gt;
[[Image:boostOffsetMap.gif]]
&lt;br&gt;
This table is an offset value that is added to the values set in the"BoostDesired Engine Load" table. The sum of the values in thesetwo tables is your desired engine load for a given RPM.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt;
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;
This table is referenced when the desired engine load differs from theactual load value. The difference in load (actual -&amp;gt; desired) isinthe left column, and the amount of correction is a variable value inthe right column. The percentage of correction is applied to thewastegate duty cycle (WGDC) to raise/lower the actual load to alignwith desired load.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;
&lt;br&gt;
[[Image:boostDesiredMap.gif]]
&lt;br&gt;
The values in this table are added to the value set in the "BoostControl Load Offset" table to determine the desired load value for agiven RPM. This table is as close as you will get to RPM based boostcontrol.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt;
&lt;br&gt;
[[Image:maxWGDCMap.gif]]
&lt;br&gt;
I'm not sure exactly how to explain this map. In it's most basicfunction, this map determines the range of control the wastegate has tocontrol boost levels. These values can be set low as a sort of firstline defense against overboost, and some tuners use this table to dialin an exact boost curve. In it's stock application, all values are setto 100%. At 100%, this map basically turns over all boost control tothe "BoostDesired Engine Load" and "Boost Control Load Offset" tables.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt;
&lt;br&gt;
[[Image:boostLimitMap.gif]]
&lt;br&gt;
This table determines the max load value considered to be safe andacceptable at a given RPM. If actual load exceeds a value in this tablefor a duration greater than the "Boost Delay Timer" value, thewastegate will open to reduce boost pressure.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;What you need to modify&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
&lt;font color="yellow"&gt;Note: Before continuing thistutorial, be sure you've saved your stock ROM in a safe place.&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
Okay. You've got you modified boost pill installed and you want to dialin your boost settings. Lets go down the list of initial changes youwill need to make.
&lt;br&gt;

&lt;br&gt;
&lt;font color="red"&gt;&lt;b&gt;WARNING:&lt;/b&gt; Do not drivethe car with the modified boost pill before flashing the ECU with yournew boost settings&amp;#33;&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt; - This map can stay where it is,but you can increase it if you feel the need.
&lt;br&gt;
&lt;b&gt;
&lt;br&gt;
Boost Control Load Offset&lt;/b&gt; - Increase this value to "100."Increasing this value will add some headroom to your "BoostDesired Engine Load" (BDEL) maps and allow for easier finetuning later.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt; - You'll want to setthe top halfof this map (negative Boost Error %) to "0" and change the values onthe lower half (positive Boost Error %) to make a gentle ramp ofcorrection with a maximum of about "-5%." See the image below ...
&lt;br&gt;

&lt;br&gt;
[[Image:boostErrorAdjusted.gif]]
&lt;br&gt;

&lt;br&gt;
These settings will protect you from overboost but not skew your loggedWastegate Duty Cycle (WGDC) values while dialing in boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;- There are 3 of these maps, and sadly, I have no idea why. Some sayone is for cold start and another for "limp" mode, but I don't thinkit's been proven. So, the easiest way to proceed is to modify all 3 ofthe maps.
&lt;br&gt;

&lt;br&gt;
Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt; - Again, there are 3 maps. Thesame thing stands ... I honestly don't know which is which. Edit all 3.
&lt;br&gt;

&lt;br&gt;
Reduce the values in the Max WGDC tables to about "30." A setting thislow is likely to not offer any boost control at all and you will likelysee only wastegate spring pressure. Don't worry, we'll be adjustingthis map a bit.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt; - Raise the values in this table to"270." If you'rea little worried about overboost you can taper these values towardredline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting yourboost. You can also adjust these values to more tolerable levels afteryou've dialed in your boost.
&lt;br&gt;

&lt;br&gt;
&lt;font color="YellowGreen"&gt;&lt;i&gt;Optional&lt;/i&gt;&lt;/font&gt;&lt;b&gt;Min Temp for Full Boost Control&lt;/b&gt;- This is another safety table that keeps you from boosting like crazybefore the car is warmed up. I lowered this value slightly to "82."
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to log&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Well, we haven't spoken much about logging. When you log, it's best tolog the full RPM range from about 2000 to 7000, much like a dyno pull.This should be done in at least 3rd gear, but 4th is preferred if youhave a safe location. You log in higher gears for several reasons:
&lt;br&gt;

&lt;br&gt;
- In higher gears boost levels are less erratic.
&lt;br&gt;
- RPM's climb slower, allowing you to log more data.
&lt;br&gt;
- The engine is under higher physical load (not directly related tologged load %) and more likely to knock, allowing for a safer tune.
&lt;br&gt;

&lt;br&gt;
When you first start logging, it's probably best to log anything andeverything you can since you will not know exactly what informationyou're looking for. As you learn more, you'll narrow down andre-arrange the information logged to suit you're tuning needs. However,you should always log these values:
&lt;br&gt;

&lt;br&gt;
TPS
&lt;br&gt;
RPM
&lt;br&gt;
Load % (i suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
&lt;br&gt;
AFR from a wideband O2
&lt;br&gt;
Boost (if possible)
&lt;br&gt;
Timing Advance
&lt;br&gt;
WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
&lt;br&gt;
and, most importantly, &lt;b&gt;KNOCK COUNT&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
Any time you log a run you will need to monitor knock count. Knock is arecord of what may be detonation or pre-ignition, which is VERY BAD foryour motor. Ideally, you always want to aim for 0 knock count over yourentire log. Sometimes a random knock count of less than 3 is acceptabledepending on how bold you are. Knock counts higher than 3 usually beginto pull timing for safety, so you definitely want to stay below thatnumber.
&lt;br&gt;

&lt;br&gt;
There is something called "phantom knock" than can be caused by shockor vibration. Phantom knock can be diagnosed by logging an additionalpull in a slightly different location. If the knock occurs in thissecond log in the same location, then it is real knock and you need toadjust your maps to compensate.
&lt;br&gt;

&lt;br&gt;
Knock is generally caused by factors you can control such as AFR, boostand timing advance. If you experience knock, look at the values in thatRPM range and you're likely to see something out of wack. You AFR mightbe too lean or too rich, you might have too much timing advance or adramatic jump in timing, or there may be a boost or load spike in thearea. The more you tune, the easier it will be to find the issue andcorrect it.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting your final boostlevels&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
To dial in your boost you'll have to log several runs. If you don'thave a way to log boost levels, it might be a good idea to have apassenger watch your boost gauge and keep you informed in casesomething were to go awry. If none of these options are available toyou, you'll just have to rely on your load levels.
&lt;br&gt;

&lt;br&gt;
Remember, your ECU is aiming to hit 240% load but is currently beinglimited by the decreased WGDC cap. As you log, you'll notice thatyou're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach yourdesired load levels while &lt;b&gt;constantly monitoring for knock&lt;/b&gt;.
&lt;br&gt;

&lt;br&gt;
If you experience knock, check your AFR and timing advance. You want anAFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower theAFR to correct for knock ... if AFR is between 10.5 and 11.3, lowertiming advance. You will be fine tuning these values later.
&lt;br&gt;

&lt;br&gt;
After several runs you should have your WGDC dialed in to where itneeds to be. When you are getting close to where you want to be, besure to compare your WGDC logs to the Max WGDC table in ECUFlash. Youmay find that the numbers you are logging are slightly lower than whatthe maps define. This is caused by the error correction table makingadjustments for overboost. Look through your log and locate theoverboost area and adjust accordingly.
&lt;br&gt;

&lt;br&gt;
Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM rangeand ramp upward after 6000 RPM to achieve a stable boost curve.Remember, we're looking for 22 psi tapering down slightly towardredline.
&lt;br&gt;

&lt;br&gt;
Once you have your boost almost exactly where you want it, add back alittle error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping youwithin +/- 2.5% of your requested load. After adding back thecorrection for the load being lower, you might see an overall increaseof about 3 in your WGDC curve. It's nothing to worry about. It'sbecause you're not at your desired load during spool up and the BCS isnow trying to correct for it. It all balances out ... that's what thistable is for.
&lt;br&gt;

&lt;br&gt;
Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]&lt;/div&gt;&lt;/div&gt;
== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
&lt;b&gt;&lt;font color="DarkOrange"&gt;VVT ... no, it's nottransmitted sexually.
&lt;br&gt;

&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;So... what now?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;
&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;Summary?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;</text>
    <sha1>189295b3a21813ceadad63994605f640ac83d654</sha1>
  </revision>
  <revision>
    <id>462</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:13:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* What you'll need */ Convert from HTML to wiki.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44359" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== &lt;b&gt;&lt;font color="DarkOrange"&gt;TB's guide to tuning with ECUFlash&lt;/font&gt;&lt;/b&gt; ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== &lt;b&gt;&lt;font color="DarkOrange"&gt;AAAHHHH&amp;#33; Lots of colors and numbers&amp;#33;&lt;/font&gt;&lt;/b&gt; ==
Alrighty, so you now have everything you need to get started. Let's getyou familiarized with the software you'll be working with.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;ECUFlash&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
ECUFlash is the application that you will use to write to and from yourECU. It comes packaged with everything you need to get started, minus aROM image from your car.
&lt;br&gt;

&lt;br&gt;
If you have your OBDII cable nearby, you can run out to your car andpull the image from it to use for this section. If you don't have acable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past thispart.
&lt;br&gt;

&lt;br&gt;
You know how to connect the OBDII cable to your car right? RIGHT? Whatdo you mean you didn't read the article I sent you to in the firstpost? Okay, fine&amp;#33; [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].
&lt;br&gt;

&lt;br&gt;
So, you're plugged in a ready to go, right? Good. Open up ECUFlash.you'll be greeted with this screen ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen01.gif]]
&lt;br&gt;

&lt;br&gt;
Now, take a second to get familiar with the buttons at the top of thescreen ...
&lt;br&gt;

&lt;br&gt;
[[Image:ecuFlashButtons.gif]]
&lt;br&gt;

&lt;br&gt;
Open ROM - This will open a saved ROM image for editing or flashing.
&lt;br&gt;
Save ROM As - This saves the edits you've made to the ROM.
&lt;br&gt;
Read From ECU - This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
&lt;br&gt;
Write to ECU - This writes the selected ROM file in ECUFlash to the ECU.
&lt;br&gt;
Test Write to ECU - The goes through the same processes as the "Writeto ECU" function, but no data is actually writted to the ECU.
&lt;br&gt;
Compare to ECU - This reads the image from the ECU and compares it tothe selected ROM image in ECUFlash. This process runs every time youwrite to the ECU, and only the modified ROM data is written to the ECU.
&lt;br&gt;

&lt;br&gt;
If you're connected to the ECU properly, the "Read from ECU" icon willbe lit. Go ahead and click the "Read from ECU" icon. You'll get thisprompt ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen02.gif]]
&lt;br&gt;

&lt;br&gt;
Select the vehicle that you are connected to and click "Read" to begintransferring your current ROM image to your computer. When the processhas finished, your screen should look similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen03.gif]]
&lt;br&gt;

&lt;br&gt;
On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and"Parameters" in the lower box. This would also be a good time to savethis ROM somewhere safe before you go poking around and changing stuff.Just click the "Save ROM As" button at the top and select a location.
&lt;br&gt;

&lt;br&gt;
(Those of you who used the ROM I linked to from above can tune back innow)
&lt;br&gt;

&lt;br&gt;
Before you start tuning, it's best that you know a little about theinformation contained in your ROM image, so I'll start there ...
&lt;br&gt;

&lt;br&gt;
The "&lt;b&gt;ROM Info&lt;/b&gt;" section contains, well, info aboutthe ROMyou're looking at. If you expand that section by clicking the little[+] to the left, you should see info that reflects the vehicle it waspulled from ...
&lt;br&gt;

&lt;br&gt;
[[Image:screen04.gif]]
&lt;br&gt;

&lt;br&gt;
Most of the info here is self explanatory, but note the value of"Internal ID." This internal ID is often referred to as the "definitionfile." In the ROM pictured above, the definition is "88590015" andhappens to be the most common Evo IX ROM.
&lt;br&gt;

&lt;br&gt;
Now, below the ROM Info section is the good stuff ... the "&lt;b&gt;Parameters&lt;/b&gt;."These Parameters hold the data that controls the variables you willharness to fine tune the performance of your Evo. The categories withinare pretty cut and dry. They include:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The fuel category includes the ever importantfuel maps,as well as more advanced info such as the MAF and injector scalingtables.
&lt;br&gt;
&lt;b&gt;Timing&lt;/b&gt; - The timing category hold your ignition andMIVEC maps.
&lt;br&gt;
&lt;b&gt;Limits&lt;/b&gt; - Within the limits category you'll find therev limit, stationary rev limit (fun fun), and speed limit tables.
&lt;br&gt;
&lt;b&gt;Turbo&lt;/b&gt; - the turbo category holds a ton of importantinfo. Thetables here control the desired boost, wastegate duty, and overboostprotection. This is probably the most confusing section of them all.
&lt;br&gt;
&lt;b&gt;Misc&lt;/b&gt; - The most important data here is theimmobilizer table.You'll need to set your user level to "Developer" to see this though.This category is also commonly used to store any tables you add to theROM definition (we'll cover this later).
&lt;br&gt;
&lt;b&gt;Idle&lt;/b&gt; - These isn't much here, but the tables withincontrol your desired idle settings.
&lt;br&gt;

&lt;br&gt;
With that out of the way, we can start looking at maps. Yay&amp;#33;
&lt;br&gt;

&lt;br&gt;
There are 3 levels of maps in ECUFlash ...
&lt;br&gt;

&lt;br&gt;
1D - A 1D map contains one address and a value for that address.
&lt;br&gt;
2D - A 2D map contains a reference column of addresses and values foreach address in a second column.
&lt;br&gt;
3D - A 3D map cross references 2 address and assigns a value based ontheir relation.
&lt;br&gt;

&lt;br&gt;
Here are some examples of the different types of maps ...
&lt;br&gt;

&lt;br&gt;
1D
&lt;br&gt;
[[Image:revLimitMap.gif]]
&lt;br&gt;

&lt;br&gt;
2D
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;

&lt;br&gt;
3D
&lt;br&gt;
[[Image:fuelMap.gif]]
&lt;br&gt;

&lt;br&gt;
3D maps can also be viewed as 3D graphs, like this one ...
&lt;br&gt;
[[Image:3dMap.gif]]
&lt;br&gt;

&lt;br&gt;
Reading the 1D and 2D maps is pretty straight forward, but the 3D mapis a little more difficult. Basically, the ECU compares the 2stationary values on the X and Y axis then assigns the corresponding Zaxis value. Take a look at the illustrations below for more clarity ...
&lt;br&gt;

&lt;br&gt;
[[Image:3dTableExplained.jpg]]
&lt;br&gt;

&lt;br&gt;
In the fuel map illustration above, the ECU is reading an engine loadvalue of "180" and an RPM value of "5500." The cell where the 180 loadcolumn and 5500 RPM row intersect decides the AFR value, which is"10.1."
&lt;br&gt;

&lt;br&gt;
Now that you know how to read the maps, you need to know how to modifythem. It is actually pretty straight forward and simple ...
&lt;br&gt;

&lt;br&gt;
"=" pops up a dialog box and allows you to directly input a value in tothe seleted cell(s).
&lt;br&gt;
"+" incrementally increases the selected value(s).
&lt;br&gt;
"-" incrementally decreases the selected value(s).
&lt;br&gt;

&lt;br&gt;
You can also copy and paste values to and from the maps using thestandard Windows CTRL+C to copy and CTRL+V to paste. If you want toknow more, check out the "Edit" menu in an open map window.
&lt;br&gt;

&lt;br&gt;
Okay, well that about sums it up for the basics of using ECU flash. Nowit's time to find out what values we need to change and why ...
== &lt;b&gt;&lt;font color="DarkOrange"&gt;Pressure predicament&lt;/font&gt;&lt;/b&gt; ==
When I first started the tune for my car, I chose to begin with settingthe boost. The reason for this was to hopefully reduce the amounttuning needed later in the process.
&lt;br&gt;

&lt;br&gt;
By first setting the amount of air being shoved on to the cylinders, Icould finish the first half of the AFR tuning without even touching thefuel maps. More importantly, the boost tables are directly related tothe load values that the ECU uses as a basis reading values from mostall of the tables that you will be editing while building your tune. Bysetting the boost first, you dial in the load values that you will beediting in the steps afterward.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Ways to tune boostpressure&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There are basically two ways to set the boost levels on your Evo. Youcan install a boost controller, or modify the factory boost controlsystem. Both have their pros and cons ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Aftermarket BoostController&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The main benefit of the boost controller option is ease of use. Thisoption gives you direct, mechanical (or electronic) control of theboost level. Some options allow you to adjust the boost on-the-fly fromthe driver's seat, and that type of control is insanely convenient.
&lt;br&gt;

&lt;br&gt;
The downside of this option is mainly the amount of control you haveover the boost levels. Some of the more expensive electroniccontrollers allow you to customize the boost curve based on RPM, butyour basic manual controller does not. Also, by disabling the stockboost control system, you forfeit the ECU's overboost protection.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Modified Stock BoostControl System&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
With this option, you have tons of control over the boost dynamics. Youcan dial out spikes and reduce taper. The method also retains the ECU'sability to reduce boost pressure in situations that might harm yourengine. There is also a cost savings with this route.
&lt;br&gt;

&lt;br&gt;
Modifying the stock boost control system is also a little tedious andtime consuming. There are many tables that interact with each other tomake it all work, and when you start tinkering with the hardware thatthese values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash theECU which requires some time and a computer.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withan aftermarket boost controller&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
This is by far the easiest and fastest method to set the boost on yourEvo. You simply remove the stock boost control system and replace itwith an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boostcontroller], so I'll just send you there in stead of wastingtime reiterating it all.
&lt;br&gt;

&lt;br&gt;
Once you have your boost controller installed, be sure to adjust it allthe way down to avoid initial overboosting. Make some runs, preferablyin 4th gear, and monitor the boost levels. Turn the boost up in smallincrements until you reach your desired boost level. Read the loggingsection further down for more info.
&lt;br&gt;

&lt;br&gt;
A stock Evo IX can easily handle 22 psi after the needle settles. Aspike of 24 or 25 psi can be expected in the peak torque area. Theboost is likely to taper down toward redline, but it should still be animprovement over stock.
&lt;br&gt;

&lt;br&gt;
If you have choosen to install a manual boost controller, you'vebasically rendered the ECU's boost control features useless, but thereare a few tables you might want to change anyway. Increasing the valuesin the "Boost Limit" table may help keep the ECU from cutting fuel inan overboost situation.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withthe stock BCS&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Grab a seat, because things are about to get interesting ...
&lt;br&gt;

&lt;br&gt;
For starters, controlling boost using the factory boost control systemisn't 100% dependent on settings in the ECU. This is due to Mitsuinstalling handy restrictor pills in the OE boost control solenoid(BCS) lines. There is one pill just before the BCS on the pressure sideand one in the short line just before the turbo. Modifying either ofthese pills will change the boost characteristics. Wrcwannabe givessome great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learnmore.
&lt;br&gt;

&lt;br&gt;
For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify thestock boost control pill for any information I give you to beapplicable. Go ahead and read through that thread and head back overhere after you have an understanding of the mechanical side ofmodifying for ECU boost control.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Boost control tables&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Before we get too far in to this stuff, you might want to set your userlevel in ECUFlash to "Developer". To do this, select "Options" from themenu up top. You'll see a user level section on the left. Open that upand select "Developer" from the pull down menu. &lt;font color="Red"&gt;WARNING&lt;/font&gt;:Changing the user level opens up many other tables that we may or maynot be using in this tutorial. If you don't know what a table is, don'tmess with it. Setting values in ECUFlash incorrectly could possiblycause irreversible damage to your Evo.
&lt;br&gt;

&lt;br&gt;
On the Evo, there are no less than six tables that control boost. Thesetables are (in order of appearance):
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt;
&lt;br&gt;
[[Image:boostDelayTimerMap.gif]]
&lt;br&gt;
This map works with the "Boost Limit" map to protect the system fromoverboost. This map is a timer (in milliseconds) that comes in to playwhen your actual boost at a given RPM exceeds the value set in the"Boost Limit" table. If boost exceeds the limit for a time greater thanthe timer's value, the wastegate is opened to lower boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Control Load Offset&lt;/b&gt;
&lt;br&gt;
[[Image:boostOffsetMap.gif]]
&lt;br&gt;
This table is an offset value that is added to the values set in the"BoostDesired Engine Load" table. The sum of the values in thesetwo tables is your desired engine load for a given RPM.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt;
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;
This table is referenced when the desired engine load differs from theactual load value. The difference in load (actual -&amp;gt; desired) isinthe left column, and the amount of correction is a variable value inthe right column. The percentage of correction is applied to thewastegate duty cycle (WGDC) to raise/lower the actual load to alignwith desired load.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;
&lt;br&gt;
[[Image:boostDesiredMap.gif]]
&lt;br&gt;
The values in this table are added to the value set in the "BoostControl Load Offset" table to determine the desired load value for agiven RPM. This table is as close as you will get to RPM based boostcontrol.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt;
&lt;br&gt;
[[Image:maxWGDCMap.gif]]
&lt;br&gt;
I'm not sure exactly how to explain this map. In it's most basicfunction, this map determines the range of control the wastegate has tocontrol boost levels. These values can be set low as a sort of firstline defense against overboost, and some tuners use this table to dialin an exact boost curve. In it's stock application, all values are setto 100%. At 100%, this map basically turns over all boost control tothe "BoostDesired Engine Load" and "Boost Control Load Offset" tables.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt;
&lt;br&gt;
[[Image:boostLimitMap.gif]]
&lt;br&gt;
This table determines the max load value considered to be safe andacceptable at a given RPM. If actual load exceeds a value in this tablefor a duration greater than the "Boost Delay Timer" value, thewastegate will open to reduce boost pressure.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;What you need to modify&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
&lt;font color="yellow"&gt;Note: Before continuing thistutorial, be sure you've saved your stock ROM in a safe place.&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
Okay. You've got you modified boost pill installed and you want to dialin your boost settings. Lets go down the list of initial changes youwill need to make.
&lt;br&gt;

&lt;br&gt;
&lt;font color="red"&gt;&lt;b&gt;WARNING:&lt;/b&gt; Do not drivethe car with the modified boost pill before flashing the ECU with yournew boost settings&amp;#33;&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt; - This map can stay where it is,but you can increase it if you feel the need.
&lt;br&gt;
&lt;b&gt;
&lt;br&gt;
Boost Control Load Offset&lt;/b&gt; - Increase this value to "100."Increasing this value will add some headroom to your "BoostDesired Engine Load" (BDEL) maps and allow for easier finetuning later.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt; - You'll want to setthe top halfof this map (negative Boost Error %) to "0" and change the values onthe lower half (positive Boost Error %) to make a gentle ramp ofcorrection with a maximum of about "-5%." See the image below ...
&lt;br&gt;

&lt;br&gt;
[[Image:boostErrorAdjusted.gif]]
&lt;br&gt;

&lt;br&gt;
These settings will protect you from overboost but not skew your loggedWastegate Duty Cycle (WGDC) values while dialing in boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;- There are 3 of these maps, and sadly, I have no idea why. Some sayone is for cold start and another for "limp" mode, but I don't thinkit's been proven. So, the easiest way to proceed is to modify all 3 ofthe maps.
&lt;br&gt;

&lt;br&gt;
Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt; - Again, there are 3 maps. Thesame thing stands ... I honestly don't know which is which. Edit all 3.
&lt;br&gt;

&lt;br&gt;
Reduce the values in the Max WGDC tables to about "30." A setting thislow is likely to not offer any boost control at all and you will likelysee only wastegate spring pressure. Don't worry, we'll be adjustingthis map a bit.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt; - Raise the values in this table to"270." If you'rea little worried about overboost you can taper these values towardredline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting yourboost. You can also adjust these values to more tolerable levels afteryou've dialed in your boost.
&lt;br&gt;

&lt;br&gt;
&lt;font color="YellowGreen"&gt;&lt;i&gt;Optional&lt;/i&gt;&lt;/font&gt;&lt;b&gt;Min Temp for Full Boost Control&lt;/b&gt;- This is another safety table that keeps you from boosting like crazybefore the car is warmed up. I lowered this value slightly to "82."
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to log&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Well, we haven't spoken much about logging. When you log, it's best tolog the full RPM range from about 2000 to 7000, much like a dyno pull.This should be done in at least 3rd gear, but 4th is preferred if youhave a safe location. You log in higher gears for several reasons:
&lt;br&gt;

&lt;br&gt;
- In higher gears boost levels are less erratic.
&lt;br&gt;
- RPM's climb slower, allowing you to log more data.
&lt;br&gt;
- The engine is under higher physical load (not directly related tologged load %) and more likely to knock, allowing for a safer tune.
&lt;br&gt;

&lt;br&gt;
When you first start logging, it's probably best to log anything andeverything you can since you will not know exactly what informationyou're looking for. As you learn more, you'll narrow down andre-arrange the information logged to suit you're tuning needs. However,you should always log these values:
&lt;br&gt;

&lt;br&gt;
TPS
&lt;br&gt;
RPM
&lt;br&gt;
Load % (i suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
&lt;br&gt;
AFR from a wideband O2
&lt;br&gt;
Boost (if possible)
&lt;br&gt;
Timing Advance
&lt;br&gt;
WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
&lt;br&gt;
and, most importantly, &lt;b&gt;KNOCK COUNT&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
Any time you log a run you will need to monitor knock count. Knock is arecord of what may be detonation or pre-ignition, which is VERY BAD foryour motor. Ideally, you always want to aim for 0 knock count over yourentire log. Sometimes a random knock count of less than 3 is acceptabledepending on how bold you are. Knock counts higher than 3 usually beginto pull timing for safety, so you definitely want to stay below thatnumber.
&lt;br&gt;

&lt;br&gt;
There is something called "phantom knock" than can be caused by shockor vibration. Phantom knock can be diagnosed by logging an additionalpull in a slightly different location. If the knock occurs in thissecond log in the same location, then it is real knock and you need toadjust your maps to compensate.
&lt;br&gt;

&lt;br&gt;
Knock is generally caused by factors you can control such as AFR, boostand timing advance. If you experience knock, look at the values in thatRPM range and you're likely to see something out of wack. You AFR mightbe too lean or too rich, you might have too much timing advance or adramatic jump in timing, or there may be a boost or load spike in thearea. The more you tune, the easier it will be to find the issue andcorrect it.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting your final boostlevels&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
To dial in your boost you'll have to log several runs. If you don'thave a way to log boost levels, it might be a good idea to have apassenger watch your boost gauge and keep you informed in casesomething were to go awry. If none of these options are available toyou, you'll just have to rely on your load levels.
&lt;br&gt;

&lt;br&gt;
Remember, your ECU is aiming to hit 240% load but is currently beinglimited by the decreased WGDC cap. As you log, you'll notice thatyou're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach yourdesired load levels while &lt;b&gt;constantly monitoring for knock&lt;/b&gt;.
&lt;br&gt;

&lt;br&gt;
If you experience knock, check your AFR and timing advance. You want anAFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower theAFR to correct for knock ... if AFR is between 10.5 and 11.3, lowertiming advance. You will be fine tuning these values later.
&lt;br&gt;

&lt;br&gt;
After several runs you should have your WGDC dialed in to where itneeds to be. When you are getting close to where you want to be, besure to compare your WGDC logs to the Max WGDC table in ECUFlash. Youmay find that the numbers you are logging are slightly lower than whatthe maps define. This is caused by the error correction table makingadjustments for overboost. Look through your log and locate theoverboost area and adjust accordingly.
&lt;br&gt;

&lt;br&gt;
Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM rangeand ramp upward after 6000 RPM to achieve a stable boost curve.Remember, we're looking for 22 psi tapering down slightly towardredline.
&lt;br&gt;

&lt;br&gt;
Once you have your boost almost exactly where you want it, add back alittle error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping youwithin +/- 2.5% of your requested load. After adding back thecorrection for the load being lower, you might see an overall increaseof about 3 in your WGDC curve. It's nothing to worry about. It'sbecause you're not at your desired load during spool up and the BCS isnow trying to correct for it. It all balances out ... that's what thistable is for.
&lt;br&gt;

&lt;br&gt;
Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]&lt;/div&gt;&lt;/div&gt;
== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
&lt;b&gt;&lt;font color="DarkOrange"&gt;VVT ... no, it's nottransmitted sexually.
&lt;br&gt;

&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;So... what now?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;
&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;Summary?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;</text>
    <sha1>b6c0715c7449cada3c87916f04ce5445d20aea9c</sha1>
  </revision>
  <revision>
    <id>464</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:24:09Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* AAAHHHH&amp;#33; Lots of colors and numbers&amp;#33; */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43808" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== &lt;b&gt;&lt;font color="DarkOrange"&gt;TB's guide to tuning with ECUFlash&lt;/font&gt;&lt;/b&gt; ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== &lt;b&gt;&lt;font color="DarkOrange"&gt;Pressure predicament&lt;/font&gt;&lt;/b&gt; ==
When I first started the tune for my car, I chose to begin with settingthe boost. The reason for this was to hopefully reduce the amounttuning needed later in the process.
&lt;br&gt;

&lt;br&gt;
By first setting the amount of air being shoved on to the cylinders, Icould finish the first half of the AFR tuning without even touching thefuel maps. More importantly, the boost tables are directly related tothe load values that the ECU uses as a basis reading values from mostall of the tables that you will be editing while building your tune. Bysetting the boost first, you dial in the load values that you will beediting in the steps afterward.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Ways to tune boostpressure&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There are basically two ways to set the boost levels on your Evo. Youcan install a boost controller, or modify the factory boost controlsystem. Both have their pros and cons ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Aftermarket BoostController&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The main benefit of the boost controller option is ease of use. Thisoption gives you direct, mechanical (or electronic) control of theboost level. Some options allow you to adjust the boost on-the-fly fromthe driver's seat, and that type of control is insanely convenient.
&lt;br&gt;

&lt;br&gt;
The downside of this option is mainly the amount of control you haveover the boost levels. Some of the more expensive electroniccontrollers allow you to customize the boost curve based on RPM, butyour basic manual controller does not. Also, by disabling the stockboost control system, you forfeit the ECU's overboost protection.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Modified Stock BoostControl System&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
With this option, you have tons of control over the boost dynamics. Youcan dial out spikes and reduce taper. The method also retains the ECU'sability to reduce boost pressure in situations that might harm yourengine. There is also a cost savings with this route.
&lt;br&gt;

&lt;br&gt;
Modifying the stock boost control system is also a little tedious andtime consuming. There are many tables that interact with each other tomake it all work, and when you start tinkering with the hardware thatthese values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash theECU which requires some time and a computer.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withan aftermarket boost controller&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
This is by far the easiest and fastest method to set the boost on yourEvo. You simply remove the stock boost control system and replace itwith an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boostcontroller], so I'll just send you there in stead of wastingtime reiterating it all.
&lt;br&gt;

&lt;br&gt;
Once you have your boost controller installed, be sure to adjust it allthe way down to avoid initial overboosting. Make some runs, preferablyin 4th gear, and monitor the boost levels. Turn the boost up in smallincrements until you reach your desired boost level. Read the loggingsection further down for more info.
&lt;br&gt;

&lt;br&gt;
A stock Evo IX can easily handle 22 psi after the needle settles. Aspike of 24 or 25 psi can be expected in the peak torque area. Theboost is likely to taper down toward redline, but it should still be animprovement over stock.
&lt;br&gt;

&lt;br&gt;
If you have choosen to install a manual boost controller, you'vebasically rendered the ECU's boost control features useless, but thereare a few tables you might want to change anyway. Increasing the valuesin the "Boost Limit" table may help keep the ECU from cutting fuel inan overboost situation.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withthe stock BCS&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Grab a seat, because things are about to get interesting ...
&lt;br&gt;

&lt;br&gt;
For starters, controlling boost using the factory boost control systemisn't 100% dependent on settings in the ECU. This is due to Mitsuinstalling handy restrictor pills in the OE boost control solenoid(BCS) lines. There is one pill just before the BCS on the pressure sideand one in the short line just before the turbo. Modifying either ofthese pills will change the boost characteristics. Wrcwannabe givessome great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learnmore.
&lt;br&gt;

&lt;br&gt;
For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify thestock boost control pill for any information I give you to beapplicable. Go ahead and read through that thread and head back overhere after you have an understanding of the mechanical side ofmodifying for ECU boost control.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Boost control tables&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Before we get too far in to this stuff, you might want to set your userlevel in ECUFlash to "Developer". To do this, select "Options" from themenu up top. You'll see a user level section on the left. Open that upand select "Developer" from the pull down menu. &lt;font color="Red"&gt;WARNING&lt;/font&gt;:Changing the user level opens up many other tables that we may or maynot be using in this tutorial. If you don't know what a table is, don'tmess with it. Setting values in ECUFlash incorrectly could possiblycause irreversible damage to your Evo.
&lt;br&gt;

&lt;br&gt;
On the Evo, there are no less than six tables that control boost. Thesetables are (in order of appearance):
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt;
&lt;br&gt;
[[Image:boostDelayTimerMap.gif]]
&lt;br&gt;
This map works with the "Boost Limit" map to protect the system fromoverboost. This map is a timer (in milliseconds) that comes in to playwhen your actual boost at a given RPM exceeds the value set in the"Boost Limit" table. If boost exceeds the limit for a time greater thanthe timer's value, the wastegate is opened to lower boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Control Load Offset&lt;/b&gt;
&lt;br&gt;
[[Image:boostOffsetMap.gif]]
&lt;br&gt;
This table is an offset value that is added to the values set in the"BoostDesired Engine Load" table. The sum of the values in thesetwo tables is your desired engine load for a given RPM.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt;
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;
This table is referenced when the desired engine load differs from theactual load value. The difference in load (actual -&amp;gt; desired) isinthe left column, and the amount of correction is a variable value inthe right column. The percentage of correction is applied to thewastegate duty cycle (WGDC) to raise/lower the actual load to alignwith desired load.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;
&lt;br&gt;
[[Image:boostDesiredMap.gif]]
&lt;br&gt;
The values in this table are added to the value set in the "BoostControl Load Offset" table to determine the desired load value for agiven RPM. This table is as close as you will get to RPM based boostcontrol.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt;
&lt;br&gt;
[[Image:maxWGDCMap.gif]]
&lt;br&gt;
I'm not sure exactly how to explain this map. In it's most basicfunction, this map determines the range of control the wastegate has tocontrol boost levels. These values can be set low as a sort of firstline defense against overboost, and some tuners use this table to dialin an exact boost curve. In it's stock application, all values are setto 100%. At 100%, this map basically turns over all boost control tothe "BoostDesired Engine Load" and "Boost Control Load Offset" tables.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt;
&lt;br&gt;
[[Image:boostLimitMap.gif]]
&lt;br&gt;
This table determines the max load value considered to be safe andacceptable at a given RPM. If actual load exceeds a value in this tablefor a duration greater than the "Boost Delay Timer" value, thewastegate will open to reduce boost pressure.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;What you need to modify&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
 '''Note: Before continuing thistutorial, be sure you've saved your stock ROM in a safe place.'''
&lt;br&gt;

&lt;br&gt;
Okay. You've got you modified boost pill installed and you want to dialin your boost settings. Lets go down the list of initial changes youwill need to make.
&lt;br&gt;

&lt;br&gt;
&lt;font color="red"&gt;&lt;b&gt;WARNING:&lt;/b&gt; Do not drivethe car with the modified boost pill before flashing the ECU with yournew boost settings&amp;#33;&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt; - This map can stay where it is,but you can increase it if you feel the need.
&lt;br&gt;
&lt;b&gt;
&lt;br&gt;
Boost Control Load Offset&lt;/b&gt; - Increase this value to "100."Increasing this value will add some headroom to your "BoostDesired Engine Load" (BDEL) maps and allow for easier finetuning later.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt; - You'll want to setthe top halfof this map (negative Boost Error %) to "0" and change the values onthe lower half (positive Boost Error %) to make a gentle ramp ofcorrection with a maximum of about "-5%." See the image below ...
&lt;br&gt;

&lt;br&gt;
[[Image:boostErrorAdjusted.gif]]
&lt;br&gt;

&lt;br&gt;
These settings will protect you from overboost but not skew your loggedWastegate Duty Cycle (WGDC) values while dialing in boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;- There are 3 of these maps, and sadly, I have no idea why. Some sayone is for cold start and another for "limp" mode, but I don't thinkit's been proven. So, the easiest way to proceed is to modify all 3 ofthe maps.
&lt;br&gt;

&lt;br&gt;
Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt; - Again, there are 3 maps. Thesame thing stands ... I honestly don't know which is which. Edit all 3.
&lt;br&gt;

&lt;br&gt;
Reduce the values in the Max WGDC tables to about "30." A setting thislow is likely to not offer any boost control at all and you will likelysee only wastegate spring pressure. Don't worry, we'll be adjustingthis map a bit.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt; - Raise the values in this table to"270." If you'rea little worried about overboost you can taper these values towardredline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting yourboost. You can also adjust these values to more tolerable levels afteryou've dialed in your boost.
&lt;br&gt;

&lt;br&gt;
&lt;font color="YellowGreen"&gt;&lt;i&gt;Optional&lt;/i&gt;&lt;/font&gt;&lt;b&gt;Min Temp for Full Boost Control&lt;/b&gt;- This is another safety table that keeps you from boosting like crazybefore the car is warmed up. I lowered this value slightly to "82."
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to log&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Well, we haven't spoken much about logging. When you log, it's best tolog the full RPM range from about 2000 to 7000, much like a dyno pull.This should be done in at least 3rd gear, but 4th is preferred if youhave a safe location. You log in higher gears for several reasons:
&lt;br&gt;

&lt;br&gt;
- In higher gears boost levels are less erratic.
&lt;br&gt;
- RPM's climb slower, allowing you to log more data.
&lt;br&gt;
- The engine is under higher physical load (not directly related tologged load %) and more likely to knock, allowing for a safer tune.
&lt;br&gt;

&lt;br&gt;
When you first start logging, it's probably best to log anything andeverything you can since you will not know exactly what informationyou're looking for. As you learn more, you'll narrow down andre-arrange the information logged to suit you're tuning needs. However,you should always log these values:
&lt;br&gt;

&lt;br&gt;
TPS
&lt;br&gt;
RPM
&lt;br&gt;
Load % (i suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
&lt;br&gt;
AFR from a wideband O2
&lt;br&gt;
Boost (if possible)
&lt;br&gt;
Timing Advance
&lt;br&gt;
WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
&lt;br&gt;
and, most importantly, &lt;b&gt;KNOCK COUNT&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
Any time you log a run you will need to monitor knock count. Knock is arecord of what may be detonation or pre-ignition, which is VERY BAD foryour motor. Ideally, you always want to aim for 0 knock count over yourentire log. Sometimes a random knock count of less than 3 is acceptabledepending on how bold you are. Knock counts higher than 3 usually beginto pull timing for safety, so you definitely want to stay below thatnumber.
&lt;br&gt;

&lt;br&gt;
There is something called "phantom knock" than can be caused by shockor vibration. Phantom knock can be diagnosed by logging an additionalpull in a slightly different location. If the knock occurs in thissecond log in the same location, then it is real knock and you need toadjust your maps to compensate.
&lt;br&gt;

&lt;br&gt;
Knock is generally caused by factors you can control such as AFR, boostand timing advance. If you experience knock, look at the values in thatRPM range and you're likely to see something out of wack. You AFR mightbe too lean or too rich, you might have too much timing advance or adramatic jump in timing, or there may be a boost or load spike in thearea. The more you tune, the easier it will be to find the issue andcorrect it.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting your final boostlevels&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
To dial in your boost you'll have to log several runs. If you don'thave a way to log boost levels, it might be a good idea to have apassenger watch your boost gauge and keep you informed in casesomething were to go awry. If none of these options are available toyou, you'll just have to rely on your load levels.
&lt;br&gt;

&lt;br&gt;
Remember, your ECU is aiming to hit 240% load but is currently beinglimited by the decreased WGDC cap. As you log, you'll notice thatyou're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach yourdesired load levels while &lt;b&gt;constantly monitoring for knock&lt;/b&gt;.
&lt;br&gt;

&lt;br&gt;
If you experience knock, check your AFR and timing advance. You want anAFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower theAFR to correct for knock ... if AFR is between 10.5 and 11.3, lowertiming advance. You will be fine tuning these values later.
&lt;br&gt;

&lt;br&gt;
After several runs you should have your WGDC dialed in to where itneeds to be. When you are getting close to where you want to be, besure to compare your WGDC logs to the Max WGDC table in ECUFlash. Youmay find that the numbers you are logging are slightly lower than whatthe maps define. This is caused by the error correction table makingadjustments for overboost. Look through your log and locate theoverboost area and adjust accordingly.
&lt;br&gt;

&lt;br&gt;
Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM rangeand ramp upward after 6000 RPM to achieve a stable boost curve.Remember, we're looking for 22 psi tapering down slightly towardredline.
&lt;br&gt;

&lt;br&gt;
Once you have your boost almost exactly where you want it, add back alittle error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping youwithin +/- 2.5% of your requested load. After adding back thecorrection for the load being lower, you might see an overall increaseof about 3 in your WGDC curve. It's nothing to worry about. It'sbecause you're not at your desired load during spool up and the BCS isnow trying to correct for it. It all balances out ... that's what thistable is for.
&lt;br&gt;

&lt;br&gt;
Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]&lt;/div&gt;&lt;/div&gt;
== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
&lt;b&gt;&lt;font color="DarkOrange"&gt;VVT ... no, it's nottransmitted sexually.
&lt;br&gt;

&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;So... what now?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;
&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;Summary?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;</text>
    <sha1>05a66f0cb96a1f9c825d5bcf9d99a1f262addc20</sha1>
  </revision>
  <revision>
    <id>465</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:24:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* TB's guide to tuning with ECUFlash */  Remove HTML in favor of wiki formatting.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43769" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== &lt;b&gt;&lt;font color="DarkOrange"&gt;Pressure predicament&lt;/font&gt;&lt;/b&gt; ==
When I first started the tune for my car, I chose to begin with settingthe boost. The reason for this was to hopefully reduce the amounttuning needed later in the process.
&lt;br&gt;

&lt;br&gt;
By first setting the amount of air being shoved on to the cylinders, Icould finish the first half of the AFR tuning without even touching thefuel maps. More importantly, the boost tables are directly related tothe load values that the ECU uses as a basis reading values from mostall of the tables that you will be editing while building your tune. Bysetting the boost first, you dial in the load values that you will beediting in the steps afterward.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Ways to tune boostpressure&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There are basically two ways to set the boost levels on your Evo. Youcan install a boost controller, or modify the factory boost controlsystem. Both have their pros and cons ...
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Aftermarket BoostController&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The main benefit of the boost controller option is ease of use. Thisoption gives you direct, mechanical (or electronic) control of theboost level. Some options allow you to adjust the boost on-the-fly fromthe driver's seat, and that type of control is insanely convenient.
&lt;br&gt;

&lt;br&gt;
The downside of this option is mainly the amount of control you haveover the boost levels. Some of the more expensive electroniccontrollers allow you to customize the boost curve based on RPM, butyour basic manual controller does not. Also, by disabling the stockboost control system, you forfeit the ECU's overboost protection.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Modified Stock BoostControl System&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
With this option, you have tons of control over the boost dynamics. Youcan dial out spikes and reduce taper. The method also retains the ECU'sability to reduce boost pressure in situations that might harm yourengine. There is also a cost savings with this route.
&lt;br&gt;

&lt;br&gt;
Modifying the stock boost control system is also a little tedious andtime consuming. There are many tables that interact with each other tomake it all work, and when you start tinkering with the hardware thatthese values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash theECU which requires some time and a computer.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withan aftermarket boost controller&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
This is by far the easiest and fastest method to set the boost on yourEvo. You simply remove the stock boost control system and replace itwith an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boostcontroller], so I'll just send you there in stead of wastingtime reiterating it all.
&lt;br&gt;

&lt;br&gt;
Once you have your boost controller installed, be sure to adjust it allthe way down to avoid initial overboosting. Make some runs, preferablyin 4th gear, and monitor the boost levels. Turn the boost up in smallincrements until you reach your desired boost level. Read the loggingsection further down for more info.
&lt;br&gt;

&lt;br&gt;
A stock Evo IX can easily handle 22 psi after the needle settles. Aspike of 24 or 25 psi can be expected in the peak torque area. Theboost is likely to taper down toward redline, but it should still be animprovement over stock.
&lt;br&gt;

&lt;br&gt;
If you have choosen to install a manual boost controller, you'vebasically rendered the ECU's boost control features useless, but thereare a few tables you might want to change anyway. Increasing the valuesin the "Boost Limit" table may help keep the ECU from cutting fuel inan overboost situation.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Controlling boost withthe stock BCS&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Grab a seat, because things are about to get interesting ...
&lt;br&gt;

&lt;br&gt;
For starters, controlling boost using the factory boost control systemisn't 100% dependent on settings in the ECU. This is due to Mitsuinstalling handy restrictor pills in the OE boost control solenoid(BCS) lines. There is one pill just before the BCS on the pressure sideand one in the short line just before the turbo. Modifying either ofthese pills will change the boost characteristics. Wrcwannabe givessome great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learnmore.
&lt;br&gt;

&lt;br&gt;
For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify thestock boost control pill for any information I give you to beapplicable. Go ahead and read through that thread and head back overhere after you have an understanding of the mechanical side ofmodifying for ECU boost control.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Boost control tables&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Before we get too far in to this stuff, you might want to set your userlevel in ECUFlash to "Developer". To do this, select "Options" from themenu up top. You'll see a user level section on the left. Open that upand select "Developer" from the pull down menu. &lt;font color="Red"&gt;WARNING&lt;/font&gt;:Changing the user level opens up many other tables that we may or maynot be using in this tutorial. If you don't know what a table is, don'tmess with it. Setting values in ECUFlash incorrectly could possiblycause irreversible damage to your Evo.
&lt;br&gt;

&lt;br&gt;
On the Evo, there are no less than six tables that control boost. Thesetables are (in order of appearance):
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt;
&lt;br&gt;
[[Image:boostDelayTimerMap.gif]]
&lt;br&gt;
This map works with the "Boost Limit" map to protect the system fromoverboost. This map is a timer (in milliseconds) that comes in to playwhen your actual boost at a given RPM exceeds the value set in the"Boost Limit" table. If boost exceeds the limit for a time greater thanthe timer's value, the wastegate is opened to lower boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Control Load Offset&lt;/b&gt;
&lt;br&gt;
[[Image:boostOffsetMap.gif]]
&lt;br&gt;
This table is an offset value that is added to the values set in the"BoostDesired Engine Load" table. The sum of the values in thesetwo tables is your desired engine load for a given RPM.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt;
&lt;br&gt;
[[Image:boostErrorMap.gif]]
&lt;br&gt;
This table is referenced when the desired engine load differs from theactual load value. The difference in load (actual -&amp;gt; desired) isinthe left column, and the amount of correction is a variable value inthe right column. The percentage of correction is applied to thewastegate duty cycle (WGDC) to raise/lower the actual load to alignwith desired load.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;
&lt;br&gt;
[[Image:boostDesiredMap.gif]]
&lt;br&gt;
The values in this table are added to the value set in the "BoostControl Load Offset" table to determine the desired load value for agiven RPM. This table is as close as you will get to RPM based boostcontrol.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt;
&lt;br&gt;
[[Image:maxWGDCMap.gif]]
&lt;br&gt;
I'm not sure exactly how to explain this map. In it's most basicfunction, this map determines the range of control the wastegate has tocontrol boost levels. These values can be set low as a sort of firstline defense against overboost, and some tuners use this table to dialin an exact boost curve. In it's stock application, all values are setto 100%. At 100%, this map basically turns over all boost control tothe "BoostDesired Engine Load" and "Boost Control Load Offset" tables.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt;
&lt;br&gt;
[[Image:boostLimitMap.gif]]
&lt;br&gt;
This table determines the max load value considered to be safe andacceptable at a given RPM. If actual load exceeds a value in this tablefor a duration greater than the "Boost Delay Timer" value, thewastegate will open to reduce boost pressure.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;What you need to modify&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
 '''Note: Before continuing thistutorial, be sure you've saved your stock ROM in a safe place.'''
&lt;br&gt;

&lt;br&gt;
Okay. You've got you modified boost pill installed and you want to dialin your boost settings. Lets go down the list of initial changes youwill need to make.
&lt;br&gt;

&lt;br&gt;
&lt;font color="red"&gt;&lt;b&gt;WARNING:&lt;/b&gt; Do not drivethe car with the modified boost pill before flashing the ECU with yournew boost settings&amp;#33;&lt;/font&gt;
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Delay Timer&lt;/b&gt; - This map can stay where it is,but you can increase it if you feel the need.
&lt;br&gt;
&lt;b&gt;
&lt;br&gt;
Boost Control Load Offset&lt;/b&gt; - Increase this value to "100."Increasing this value will add some headroom to your "BoostDesired Engine Load" (BDEL) maps and allow for easier finetuning later.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Turbo Boost Error Correction&lt;/b&gt; - You'll want to setthe top halfof this map (negative Boost Error %) to "0" and change the values onthe lower half (positive Boost Error %) to make a gentle ramp ofcorrection with a maximum of about "-5%." See the image below ...
&lt;br&gt;

&lt;br&gt;
[[Image:boostErrorAdjusted.gif]]
&lt;br&gt;

&lt;br&gt;
These settings will protect you from overboost but not skew your loggedWastegate Duty Cycle (WGDC) values while dialing in boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;BoostDesired Engine Load&lt;/b&gt;- There are 3 of these maps, and sadly, I have no idea why. Some sayone is for cold start and another for "limp" mode, but I don't thinkit's been proven. So, the easiest way to proceed is to modify all 3 ofthe maps.
&lt;br&gt;

&lt;br&gt;
Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Max Wastegate Duty&lt;/b&gt; - Again, there are 3 maps. Thesame thing stands ... I honestly don't know which is which. Edit all 3.
&lt;br&gt;

&lt;br&gt;
Reduce the values in the Max WGDC tables to about "30." A setting thislow is likely to not offer any boost control at all and you will likelysee only wastegate spring pressure. Don't worry, we'll be adjustingthis map a bit.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Boost Limit&lt;/b&gt; - Raise the values in this table to"270." If you'rea little worried about overboost you can taper these values towardredline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting yourboost. You can also adjust these values to more tolerable levels afteryou've dialed in your boost.
&lt;br&gt;

&lt;br&gt;
&lt;font color="YellowGreen"&gt;&lt;i&gt;Optional&lt;/i&gt;&lt;/font&gt;&lt;b&gt;Min Temp for Full Boost Control&lt;/b&gt;- This is another safety table that keeps you from boosting like crazybefore the car is warmed up. I lowered this value slightly to "82."
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to log&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Well, we haven't spoken much about logging. When you log, it's best tolog the full RPM range from about 2000 to 7000, much like a dyno pull.This should be done in at least 3rd gear, but 4th is preferred if youhave a safe location. You log in higher gears for several reasons:
&lt;br&gt;

&lt;br&gt;
- In higher gears boost levels are less erratic.
&lt;br&gt;
- RPM's climb slower, allowing you to log more data.
&lt;br&gt;
- The engine is under higher physical load (not directly related tologged load %) and more likely to knock, allowing for a safer tune.
&lt;br&gt;

&lt;br&gt;
When you first start logging, it's probably best to log anything andeverything you can since you will not know exactly what informationyou're looking for. As you learn more, you'll narrow down andre-arrange the information logged to suit you're tuning needs. However,you should always log these values:
&lt;br&gt;

&lt;br&gt;
TPS
&lt;br&gt;
RPM
&lt;br&gt;
Load % (i suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
&lt;br&gt;
AFR from a wideband O2
&lt;br&gt;
Boost (if possible)
&lt;br&gt;
Timing Advance
&lt;br&gt;
WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
&lt;br&gt;
and, most importantly, &lt;b&gt;KNOCK COUNT&lt;/b&gt;
&lt;br&gt;

&lt;br&gt;
Any time you log a run you will need to monitor knock count. Knock is arecord of what may be detonation or pre-ignition, which is VERY BAD foryour motor. Ideally, you always want to aim for 0 knock count over yourentire log. Sometimes a random knock count of less than 3 is acceptabledepending on how bold you are. Knock counts higher than 3 usually beginto pull timing for safety, so you definitely want to stay below thatnumber.
&lt;br&gt;

&lt;br&gt;
There is something called "phantom knock" than can be caused by shockor vibration. Phantom knock can be diagnosed by logging an additionalpull in a slightly different location. If the knock occurs in thissecond log in the same location, then it is real knock and you need toadjust your maps to compensate.
&lt;br&gt;

&lt;br&gt;
Knock is generally caused by factors you can control such as AFR, boostand timing advance. If you experience knock, look at the values in thatRPM range and you're likely to see something out of wack. You AFR mightbe too lean or too rich, you might have too much timing advance or adramatic jump in timing, or there may be a boost or load spike in thearea. The more you tune, the easier it will be to find the issue andcorrect it.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting your final boostlevels&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
To dial in your boost you'll have to log several runs. If you don'thave a way to log boost levels, it might be a good idea to have apassenger watch your boost gauge and keep you informed in casesomething were to go awry. If none of these options are available toyou, you'll just have to rely on your load levels.
&lt;br&gt;

&lt;br&gt;
Remember, your ECU is aiming to hit 240% load but is currently beinglimited by the decreased WGDC cap. As you log, you'll notice thatyou're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach yourdesired load levels while &lt;b&gt;constantly monitoring for knock&lt;/b&gt;.
&lt;br&gt;

&lt;br&gt;
If you experience knock, check your AFR and timing advance. You want anAFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower theAFR to correct for knock ... if AFR is between 10.5 and 11.3, lowertiming advance. You will be fine tuning these values later.
&lt;br&gt;

&lt;br&gt;
After several runs you should have your WGDC dialed in to where itneeds to be. When you are getting close to where you want to be, besure to compare your WGDC logs to the Max WGDC table in ECUFlash. Youmay find that the numbers you are logging are slightly lower than whatthe maps define. This is caused by the error correction table makingadjustments for overboost. Look through your log and locate theoverboost area and adjust accordingly.
&lt;br&gt;

&lt;br&gt;
Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM rangeand ramp upward after 6000 RPM to achieve a stable boost curve.Remember, we're looking for 22 psi tapering down slightly towardredline.
&lt;br&gt;

&lt;br&gt;
Once you have your boost almost exactly where you want it, add back alittle error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping youwithin +/- 2.5% of your requested load. After adding back thecorrection for the load being lower, you might see an overall increaseof about 3 in your WGDC curve. It's nothing to worry about. It'sbecause you're not at your desired load during spool up and the BCS isnow trying to correct for it. It all balances out ... that's what thistable is for.
&lt;br&gt;

&lt;br&gt;
Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]&lt;/div&gt;&lt;/div&gt;
== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
&lt;b&gt;&lt;font color="DarkOrange"&gt;VVT ... no, it's nottransmitted sexually.
&lt;br&gt;

&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;So... what now?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;
&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;Summary?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;</text>
    <sha1>b0d0e98f6d1ca8b4f6fd7185a92bfa2182e91129</sha1>
  </revision>
  <revision>
    <id>466</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:43:45Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Pressure predicament */ HTML to wiki conversion.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42816" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

;Boost Delay Timer
:[[Image:boostDelayTimerMap.gif]]
:This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

;Boost Control Load Offset
:[[Image:boostOffsetMap.gif]]
:This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

;Turbo Boost Error Correction
:[[Image:boostErrorMap.gif]]
:This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

;BoostDesired Engine Load
:[[Image:boostDesiredMap.gif]]
:The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

;Max Wastegate Duty
:[[Image:maxWGDCMap.gif]]
:I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

;Boost Limit
:[[Image:boostLimitMap.gif]]
:This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

;Boost Delay Timer
:This map can stay where it is,but you can increase it if you feel the need.

;Boost Control Load Offset
:Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

;Turbo Boost Error Correction
:You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

:These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

;BoostDesired Engine Load
:There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.
:Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

;Max Wastegate Duty
:Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.
:Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

;Boost Limit
:Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

;''(Optional)'' Min Temp for Full Boost Control
:This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
&lt;b&gt;&lt;font color="DarkOrange"&gt;VVT ... no, it's nottransmitted sexually.
&lt;br&gt;

&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;So... what now?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;
&lt;br&gt;
&lt;/font&gt;&lt;/b&gt;&lt;b&gt;&lt;font color="DarkOrange"&gt;Summary?&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;</text>
    <sha1>26a854e4a4cab437508092b94dd1a91182745c4b</sha1>
  </revision>
  <revision>
    <id>453</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:44:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* [Missing Sections] */ HTML to wiki.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42651" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

;Boost Delay Timer
:[[Image:boostDelayTimerMap.gif]]
:This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

;Boost Control Load Offset
:[[Image:boostOffsetMap.gif]]
:This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

;Turbo Boost Error Correction
:[[Image:boostErrorMap.gif]]
:This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

;BoostDesired Engine Load
:[[Image:boostDesiredMap.gif]]
:The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

;Max Wastegate Duty
:[[Image:maxWGDCMap.gif]]
:I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

;Boost Limit
:[[Image:boostLimitMap.gif]]
:This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

;Boost Delay Timer
:This map can stay where it is,but you can increase it if you feel the need.

;Boost Control Load Offset
:Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

;Turbo Boost Error Correction
:You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

:These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

;BoostDesired Engine Load
:There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.
:Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

;Max Wastegate Duty
:Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.
:Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

;Boost Limit
:Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

;''(Optional)'' Min Temp for Full Boost Control
:This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
&lt;/font&gt;&lt;/b&gt;You're half way there ... let's move on to setting the timing. Now, the"timing" I'm talking about here it the adjustment of the moment whenthe spark plug fires to ignite the fuel.
&lt;br&gt;

&lt;br&gt;
There are 3 high octane timing maps, and 3 low octane timing maps onyour Evo IX. These high and low octane maps work the same as the fuelmaps ... if knock is encountered for an extended period of time, someinterpolation will occur. You want to focus on the high octane mapsright now.
&lt;br&gt;

&lt;br&gt;
If you compare the 3 high octane maps, you'll notice that they are notthe same. Map #2 is a little more aggressive with more advance acrossmost of the map. As mentioned earlier, it's speculated that the #2 mapis the main map used during normal operating conditions. I'vepersonally found that interpolation occurs across (mainly) the #2 and#3 maps even when no knock is present.
&lt;br&gt;

&lt;br&gt;
So, the tactic I've found most useful is setting all of the high octanemaps with the same values. This produces dependable results and makesyour life a lot simpler. Don't worry ... if something goes wrong,you'll still have the low octane maps to keep the car safe.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Let's talk theory&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
There is a theory that many tuners use as a guide for tuning timing.It's referred to as "Minimum Timing for Best Torque" (MTBT).
&lt;br&gt;

&lt;br&gt;
Looking at tuning from the most basic sense, timing advance makespower. This is what some tuners will set the timing unusually high andlet the ECU's built in safety features correct for it ... more on thatlater. However, it is believed that there is a point where advancingthe timing does not produce extra power ... it simple makes the enginemore prone to knock. So, according to the MTBT theory, the best way toset timing advance is to advance it until you don't gain any morepower. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.
&lt;br&gt;

&lt;br&gt;
The MTBT theory is based on an absolute fact that an engine willproduce the most power when peak cylinder pressure occurs at 15* pasttop dead center (TDC). This is the point in the ignition stroke wherethe rod has the most leverage to turn the crank. Now, you might thinkthat 15* is an absolute number that we are aiming for, but it's not. Wecan control when the spark fires, but that doesn't mean at that exactmoment the cylinder pressure is at it's greatest ... it's an involvedprocess. We must consider the gap and temperature of the plug, the timeit takes for the fuel to reach its maximum potential and the speed atwhich the engine is spinning.
&lt;br&gt;

&lt;br&gt;
To use this method of tuning, you'll need some way to measure the poweroutput of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer].But, dyno time is expensive and tuning takes time. Some of us don'treally have much of either. There are other solutions though ... youcan use some pretty complex equations and create your own road dyno.This will allow you to measure your cars performance based only on thevalues you can log from your ECU. You do need to know some vital infothough .. such as vehicle weight, drag coefficient, gear ratios,frontal area of the vehicle, ambient temps, etc. Many self tuners use [http://www.dataloglab.com/ DataLog Lab]for this analysis. EvoScan also has a power/torque calculation featurebuilt in to the graph viewer, but I've found it do be only marginallyuseful.
&lt;br&gt;

&lt;br&gt;
The best road dyno solution I've found so far is offered by a fellowEvo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator]is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from yourlog. You'll get a result similar to this ...
&lt;br&gt;

&lt;br&gt;
(Image to come)
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="YellowGreen"&gt;Note:&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
When using a road dyno your results will not be as accurate as anactual dynamometer. Since the calculations are based mainly on RPM gainover time, the actual road surface you choose can skew the numbersproduced. It is highly recommended that you only compare data recordedon the same stretch of road if you want reliable results.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Time to make some actualchanges&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
Timing can be advanced (+) or retarded (-) in regard to TDC (0).Advanced timing means that the spark fires before TDC and retardedmeans ignition occurs after TDC. I know it seems backward, but trust me.
&lt;br&gt;

&lt;br&gt;
We are aiming for peak pressue at the magical 15* ATDC. Now, lets lookat the individual components that affect this peak pressue and when itoccurs:
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;RPM&lt;/b&gt; - The speed the engine is spinning. This one issimple. Thefaster the engine is spinning, the earlier the spark has to fire forthe burn to keep up.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Fuel&lt;/b&gt; - The A:F mix affects the length of the fuelburn in thecylinder. A leaner mix will burn faster, and will therefore requireless advance to hit the 15* mark. The opposite is true for a richermix. The added fuel will take longer to burn and will require moreadvance.
&lt;br&gt;

&lt;br&gt;
Also, the fuel octane should be considered here as well. The octanelevel doesn't really affect the timing needed, but more so the timingrange available while avoiding knock. 87 octane fuel will burn exactlylike 93, but you are less likely to reach your desired ignition pointon 87 before you encounter pre-ignition.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;Spark&lt;/b&gt; - The spark is probably the most crucialcomponent in thisarray of variables. The heat range and gap of the plug play a veryimportant role in the process. A "colder" (lower heat range) plug willslow the burn of the fuel and reduce the chance of knock by keepingcylinder temps and the temperature of the plug tip itself lower. Thisis important for us because cylinder pressures are generally higher inforced induction engines ... this increased pressure combined withexcess heat is usually the cause of knock.
&lt;br&gt;

&lt;br&gt;
&lt;font color="Green"&gt;Note: &lt;/font&gt;The basic rule isthat you need to go 1 heat range colder after adding 100hp to the car.
&lt;br&gt;

&lt;br&gt;
The material of which the spark plug's electrode is made should also beconsidered. Our cars come equipped with iridium plugs. Iridium is usedas an electrode material because it does not corrode or melt in thecylinder like plugs of the past. This property creates a reliable sparkover an extended period of time. Some people choose to run copper plugsfor their increased conductivity. This is an advantage and is likely togive a slight increase in power. However, copper electrodes wearextremely fast in our cars and need to be changed every 5000 miles orearlier.
&lt;br&gt;

&lt;br&gt;
Basically, if you have some power mods on your Evo you want to run acolder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it'sracing series, which is R7437-8). The plug gap should be on the highend of factory spec for best performance. Gap for the IX should bebetween .020 and .024. This kind of sucks because replacement plugscome at .044 or .032, which will likely cause misfire issues. Maybe thedealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044.Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].
&lt;br&gt;

&lt;br&gt;
(still adding ...)
== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>10ed6b6031c930dface8dd4191ef4edbb1728920</sha1>
  </revision>
  <revision>
    <id>467</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:52:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Excuse me, do you have the timing? */  HTML to wiki.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42370" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

;Boost Delay Timer
:[[Image:boostDelayTimerMap.gif]]
:This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

;Boost Control Load Offset
:[[Image:boostOffsetMap.gif]]
:This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

;Turbo Boost Error Correction
:[[Image:boostErrorMap.gif]]
:This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

;BoostDesired Engine Load
:[[Image:boostDesiredMap.gif]]
:The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

;Max Wastegate Duty
:[[Image:maxWGDCMap.gif]]
:I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

;Boost Limit
:[[Image:boostLimitMap.gif]]
:This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

;Boost Delay Timer
:This map can stay where it is,but you can increase it if you feel the need.

;Boost Control Load Offset
:Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

;Turbo Boost Error Correction
:You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

:These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

;BoostDesired Engine Load
:There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.
:Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

;Max Wastegate Duty
:Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.
:Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

;Boost Limit
:Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

;''(Optional)'' Min Temp for Full Boost Control
:This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== &lt;b&gt;&lt;font color="DarkOrange"&gt;For richer or leaner&lt;/font&gt;&lt;/b&gt; ==
Woo Hoo&amp;#33; You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.
&lt;br&gt;

&lt;br&gt;
As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhatadvanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune forspecific fuel ratios.
&lt;br&gt;

&lt;br&gt;
*snore*
&lt;br&gt;

&lt;br&gt;
... Aaahhh&amp;#33; Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.
&lt;br&gt;

&lt;br&gt;
Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.
&lt;br&gt;

&lt;br&gt;
Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.
&lt;br&gt;

&lt;br&gt;
So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Some things to consider&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...
&lt;br&gt;

&lt;br&gt;
The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.
&lt;br&gt;

&lt;br&gt;
Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and thereis a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.
&lt;br&gt;

&lt;br&gt;
Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.
&lt;br&gt;

&lt;br&gt;
[[Image:leanSpoolCompare.gif]]
&lt;br&gt;

&lt;br&gt;
Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Yourlogging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.
&lt;br&gt;

&lt;br&gt;
&lt;b&gt;&lt;font color="DarkOrange"&gt;Setting a nice fuel curve&lt;/font&gt;&lt;/b&gt;
&lt;br&gt;
So, now we know what we are aiming for and we can begin tuning. You canstart your fuel tuning based on your final boost log. Here is what youwant to do:
&lt;br&gt;

&lt;br&gt;
From 3500 RPM to about 6000 RPM you want to aim for an AFR of about11.2:1. This is a safe value for pump gas. With higher octane fuel youcan go leaner.
&lt;br&gt;

&lt;br&gt;
Here is a trick for you ... remember that magical 12.6:1 AFR Imentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much lesslikely to knock. This is because without boost, our engines are justlow compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than thebasic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turboreach full boost about 250 RPM sooner.
&lt;br&gt;

&lt;br&gt;
At the high end of the revs, it's a good idea to gradually richen themix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safevalue at 7000+ RPM. Ramp down to this value starting around 6000 RPM.
&lt;br&gt;

&lt;br&gt;
Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing orreduce boost if there is a spike.
&lt;br&gt;

&lt;br&gt;
You're looking for something similar to this ...
&lt;br&gt;

&lt;br&gt;
[[Image:fuelCurve.gif]]
&lt;br&gt;

&lt;br&gt;
See, the process is getting a little easier now, huh?&lt;b&gt;&lt;font color="DarkOrange"&gt;
== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

The best road dyno solution I've found so far is offered by a fellow Evo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator] is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from your log. You'll get a result similar to this ...

(Image to come)

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>a1259797fd87e6050bfd46609184dfe49974d6c6</sha1>
  </revision>
  <revision>
    <id>468</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:54:45Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* For richer or leaner */ HTML to wiki.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42036" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

;Boost Delay Timer
:[[Image:boostDelayTimerMap.gif]]
:This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

;Boost Control Load Offset
:[[Image:boostOffsetMap.gif]]
:This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

;Turbo Boost Error Correction
:[[Image:boostErrorMap.gif]]
:This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

;BoostDesired Engine Load
:[[Image:boostDesiredMap.gif]]
:The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

;Max Wastegate Duty
:[[Image:maxWGDCMap.gif]]
:I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

;Boost Limit
:[[Image:boostLimitMap.gif]]
:This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

;Boost Delay Timer
:This map can stay where it is,but you can increase it if you feel the need.

;Boost Control Load Offset
:Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

;Turbo Boost Error Correction
:You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

:These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

;BoostDesired Engine Load
:There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.
:Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

;Max Wastegate Duty
:Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.
:Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

;Boost Limit
:Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

;''(Optional)'' Min Temp for Full Boost Control
:This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

The best road dyno solution I've found so far is offered by a fellow Evo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator] is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from your log. You'll get a result similar to this ...

(Image to come)

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>552de67fb1795f20685b567bc6abbc49d0daff7b</sha1>
  </revision>
  <revision>
    <id>469</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:55:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost control tables */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42066" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

;Boost Delay Timer
:This map can stay where it is,but you can increase it if you feel the need.

;Boost Control Load Offset
:Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

;Turbo Boost Error Correction
:You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

:These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

;BoostDesired Engine Load
:There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.
:Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

;Max Wastegate Duty
:Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.
:Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

;Boost Limit
:Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

;''(Optional)'' Min Temp for Full Boost Control
:This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

The best road dyno solution I've found so far is offered by a fellow Evo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator] is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from your log. You'll get a result similar to this ...

(Image to come)

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>716e8e831cbb69a7c9c71c51ac16e84123a51d67</sha1>
  </revision>
  <revision>
    <id>470</id>
    <parentid>451</parentid>
    <timestamp>2008-08-06T17:56:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* What you need to modify */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42107" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[http://www.openecu.org/ ECUFlash]- Yes, let's assume you need the tuning software to tune your ECU. This is open source software and a free download.

===Logging Software===
[http://www.limitless.co.nz/evoscan/ EvoScan]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.


Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[http://www.tactrix.com/ TactrixCable] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors.This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they stop giving feedback at a certain load or throttle percentage and the car enters "open loop" mode. This brings us to ...

&lt;b&gt;Open loop&lt;/b&gt; occurs when the vehicle stops relying on the O2sensors to give it feedback on the car's air to fuel mixture. Basically, in open loop mode, the ECU aims for a set fuel mixture and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing anextra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher range of the sensor allows for more accurate readings.

Here are some common wideband O2 choices ...

[http://www.innovatemotorsports.com/products/lc1.php Innovate LC-1]- This is a basic, minimal wideband setup. It includes the 5v O2sensor, computer interface, and the LogWorks software mentioned earlier. This is the setup that I use, and I found it [http://www.axceleratedmotorsports.com/Details.cfm?ProdID=47 here] at a good price.

[http://www.zeitronix.com/Products/zt2/zt2.htm Zeitronics ZT-2]- This is a popular option as well. The benefit of the Zeitronics setup over the LC-1 is the option of an LCD display panel and a control module to interface with other sensors to monitor things such as boost pressure and exhaust gas temperatures. Innovate offers similar options if you upgrade to the LM-1 unit.

There are of course other options for wideband O2 sensors and most will be supported by the logger you choose.

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately log boost levels with your logs.This should give you the same readings as your mechanical boost gauge,but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get someinfo in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most common Evo IX ROM.

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit (fun fun), and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store any tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 stationary values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustrations below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the AFR value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not. Also, by disabling the stock boost control system, you forfeit the ECU's overboost protection.

===Modified Stock Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route.

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. Increasing the values in the "Boost Limit" table may help keep the ECU from cutting fuel in an overboost situation.

===Controlling boost with the stock BCS===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

For this tutorial, we'll be using [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control].You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu. '''''WARNING:''''' Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the wastegate is opened to lower boost.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
I'm not sure exactly how to explain this map. In it's most basic function, this map determines the range of control the wastegate has to control boost levels. These values can be set low as a sort of first line defense against overboost, and some tuners use this table to dial in an exact boost curve. In it's stock application, all values are set to 100%. At 100%, this map basically turns over all boost control to the "Boost Desired Engine Load" and "Boost Control Load Offset" tables.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill before flashing the ECU with your new boost settings!

====Boost Delay Timer====
This map can stay where it is,but you can increase it if you feel the need.

====Boost Control Load Offset====
Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

====Turbo Boost Error Correction====
You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

====BoostDesired Engine Load====
There are 3 of these maps, and sadly, I have no idea why. Some say one is for cold start and another for "limp" mode, but I don't think it's been proven. So, the easiest way to proceed is to modify all 3 of the maps.

Set the BDEL in all 3 maps to "140" with a slight taper down to "130"from 5500 RPM to 7000 RPM. This value added to the load offset value of"100" gives you a desired load of "240" through most of the rev bandwhich is equal to about 22 psi. We're tapering down the top end toreduce the chance of knock.

====Max Wastegate Duty====
Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.

Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

====Boost Limit====
Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

====Min Temp for Full Boost Control====
''(Optional)'' This is another safety table that keeps you from boosting like crazy before the car is warmed up. I lowered this value slightly to "82."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable depending on how bold you are. Knock counts higher than 3 usually begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location. If the knock occurs in this second log in the same location, then it is real knock and you need to adjust your maps to compensate.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC cap. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at-2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for the load being lower, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, theless stable it is under pressure and therefore more likely to spontaneously combust in to pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

The values in the fuel map are not actual AFR values. They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This really doesn't effect your tuning other than throwing off the values even in the fuel map even more. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should have an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12sup to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and make small,gradual changes. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways,such as a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://www.topspeedsales.com/%284worwm45bfvxfg4525aoxdzc%29/default.aspx?vc=tuning dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

The best road dyno solution I've found so far is offered by a fellow Evo tuner you may know as "mrfred." His [http://forums.evolutionm.net/showthread.php?t=276205 Excel based power/torque calculator] is free, easy to use, and accurate. Plus, it's already set up for an IXMR. All you have to do is paste in the RPM and time values from your log. You'll get a result similar to this ...

(Image to come)

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>d3585da55c8c739dee41d2e0774005e898009cf9</sha1>
  </revision>
</page>
<page arvcontinue="20080729212749|248">
  <title>Glossary</title>
  <ns>0</ns>
  <id>130</id>
  <revision>
    <id>541</id>
    <parentid>536</parentid>
    <timestamp>2008-08-08T15:09:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1028" xml:space="preserve">A/C - Air Con

AIT - Air Intake Temperature

AFR - Air/Fuel Ratio

Baro - Barometer/Barometric

BCS - Boost Control System

BDEL - Boost Desired Engine Load

BTDC - Before Top Dead Center

BWGD - Base Wastegate Duty

CEL/SES - Check Engine Light/Service Engine Soon

DLL - [[Data Log Lab]]

ECU - Engine Control unit

EDM - European Domestic Market

EGR - Exhaust Gas Recirculation

IAT - Intake Air Temperature

ICS - Inter Cooler Spray

IDC - Injector Duty Cycle

IGN - Ignintion

IPW - Injector Pulse Width

JDM - Japanese Domestic Market

LTFT - Long Term Fuel Trim

MAF - Mass Air Flow

MAP - Manifold Absolute Pressure

MUT - Multi Use Tester

NLTS - No Lift To Shift

02/NB0 - Oxygen Sensor (Narrow Band)

RPM - Rev Per Minute

SAS - Speed Adjusting Screw

STFT - Short Term Fuel Trim

TBEC - Turbo Boost Error Correction

TPS - Throttle Position Sensor

USDM - United States Domestic Market

WB02 - Wideband Oxygen Sensor

WGDC - Wastegate Duty Cycle

WGDCCorr - Wastegate Duty Cycle Correction

WOT - Wide Open Throttle</text>
    <sha1>d2b98dd62e8991ca922f591d7729a3407493531f</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>3 Port Boost Control</title>
  <ns>0</ns>
  <id>139</id>
  <revision>
    <id>604</id>
    <parentid>603</parentid>
    <timestamp>2008-08-13T21:57:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* What you will need: */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3670" xml:space="preserve">Can be integrated with [[Patching#Direct_Boost_Control_.28PSI.29|direct boost control]]

Original Thread [[http://forums.evolutionm.net/showthread.php?p=5504930 here]]

Risks:  While this solution is fairly straightforward it is very possible for you to screw something up.  Too high of duty cycles or lines that are not arranged properly will cause boost overshoot and possibly cause serious damage!  If a solenoid fails and you are using the interrupt method generally used with a 3 port (stock is bleed-type) you run the risk of overshoot also.  Most solenoids will fail in their normally open (NO) position, but it is possible for one to fail in its normally closed (NC) position.  Please take this into consideration when doing this mod!

== Installation ==


=== What you will need: ===
* The ability to tune your ECU. '''''IMPORTANT!''''' You '''MUST''' reduce your boost tables before your first drive.  If you do not you will overshoot and serious damage may occur!

* A compatible 3 port solenoid.  Known Solenoids include (but are not limited to):

{|border="1"
|+Known Compatible Solenoids
!Make
!Part # (if applicable)
!Similar to
|-
|AC Delco || 214-474, PT374 (pigtail) || GM
|-
|GM || [[http://www.gmpartsdirect.com/results.cfm?partnumber=1997152 1997152]], 12102747 (pigtail) || AC Delco
|-
|Perrin || EBCS || INGERSOLL-RAND
|-
|INGERSOLL-RAND || [[http://www.grainger.com/Grainger/wwg/itemDetailsRender.shtml?ItemId=1612667260 P251SS-012-D]] || Perrin EBCS (coated, comes with fittings, possibly other mods)
|-
|AEM|| #30-2400 or Tru-Boost part || Mac Valves (below)
|-
|MAC|| 36A-AAA-JDBA-1BA || AEM
|-
|MAC|| 36A-AAA-JDBA-1GD || AEM (extra connector on solenoid and LED indicator)
|-
|Tactrix|| PD3PBCSM || None
|}

* A way to connect the solenoid to the stock wiring.  Some people use simple crimp ons, some use vampire clips (not recommended!) or solder the the OEM harness.  The Tactrix Solenoid is PNP.  GST motorsports was rumored to have connectors at one point, but this cannot be confirmed.  You can also harvest the AC Pressure sensor off of many common DSM (or mitsubishi in general) including the evo for a PNP solution (see [[http://forums.evolutionm.net/showpost.php?p=5459266&amp;postcount=52 here]], [[http://forums.evolutionm.net/showpost.php?p=5462962&amp;postcount=53 here]], and [[http://forums.evolutionm.net/showpost.php?p=5504930&amp;postcount=253 here]] ).

* A resistor for any of the non Tactrix Solenoids.  This piece is debatable, but the original reason is to prevent the ECU from sending too much current and causing damage to the solenoid or ECU itself.  This has been confirmed to work on the GM and AEM/MAC solenoids.

=== Flash your ECU ===
Reduce all of your Max WGDC (sometimes called Base WGDC) tables to 50% to prevent overshoot.  Then see a [[How_to_Tune_an_Evo_TB_Alternate|tuning guide]] for how to tune your boost when you are finished with the install.

=== Install the Solenoid ===
Wire orientation should not matter.  Install the resistor in line and solder your connections or create a PNP connector.

=== Tune ===
Then tune, tune, and tune again until your tables are spot on!  Enjoy increased boost holding capacity and control.


Also, when using this method it may be a good idea to raise the values for BCS de-activation RPM.  Stock these are set to 7500.  If you reach 7500 RPM on throttle your WGDC will jump to 100% with these values.  Raise them above your rev-limit to have them continue to interpolate to that RPM.
[[Image:BCS_deactivation_RPM.JPG|center|BCS deactivation RPM]]
Be careful and make sure your XML definitions are correct before modifying this value.  This table is often defined incorrectly.</text>
    <sha1>197a4680fc393d325009d3e9ac9f5406ad07f857</sha1>
  </revision>
  <revision>
    <id>610</id>
    <parentid>609</parentid>
    <timestamp>2008-08-14T01:06:31Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Corrected URL for original thread.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3669" xml:space="preserve">Can be integrated with [[Patching#Direct_Boost_Control_.28PSI.29|direct boost control]]

Original Thread [[http://forums.evolutionm.net/showthread.php?t=276674 here]]

Risks:  While this solution is fairly straightforward it is very possible for you to screw something up.  Too high of duty cycles or lines that are not arranged properly will cause boost overshoot and possibly cause serious damage!  If a solenoid fails and you are using the interrupt method generally used with a 3 port (stock is bleed-type) you run the risk of overshoot also.  Most solenoids will fail in their normally open (NO) position, but it is possible for one to fail in its normally closed (NC) position.  Please take this into consideration when doing this mod!

== Installation ==


=== What you will need: ===
* The ability to tune your ECU. '''''IMPORTANT!''''' You '''MUST''' reduce your boost tables before your first drive.  If you do not you will overshoot and serious damage may occur!

* A compatible 3 port solenoid.  Known Solenoids include (but are not limited to):

{|border="1"
|+Known Compatible Solenoids
!Make
!Part # (if applicable)
!Similar to
|-
|AC Delco || 214-474, PT374 (pigtail) || GM
|-
|GM || [[http://www.gmpartsdirect.com/results.cfm?partnumber=1997152 1997152]], 12102747 (pigtail) || AC Delco
|-
|Perrin || EBCS || INGERSOLL-RAND
|-
|INGERSOLL-RAND || [[http://www.grainger.com/Grainger/wwg/itemDetailsRender.shtml?ItemId=1612667260 P251SS-012-D]] || Perrin EBCS (coated, comes with fittings, possibly other mods)
|-
|AEM|| #30-2400 or Tru-Boost part || Mac Valves (below)
|-
|MAC|| 36A-AAA-JDBA-1BA || AEM
|-
|MAC|| 36A-AAA-JDBA-1GD || AEM (extra connector on solenoid and LED indicator)
|-
|Tactrix|| PD3PBCSM || None
|}

* A way to connect the solenoid to the stock wiring.  Some people use simple crimp ons, some use vampire clips (not recommended!) or solder the the OEM harness.  The Tactrix Solenoid is PNP.  GST motorsports was rumored to have connectors at one point, but this cannot be confirmed.  You can also harvest the AC Pressure sensor off of many common DSM (or mitsubishi in general) including the evo for a PNP solution (see [[http://forums.evolutionm.net/showpost.php?p=5459266&amp;postcount=52 here]], [[http://forums.evolutionm.net/showpost.php?p=5462962&amp;postcount=53 here]], and [[http://forums.evolutionm.net/showpost.php?p=5504930&amp;postcount=253 here]] ).

* A resistor for any of the non Tactrix Solenoids.  This piece is debatable, but the original reason is to prevent the ECU from sending too much current and causing damage to the solenoid or ECU itself.  This has been confirmed to work on the GM and AEM/MAC solenoids.

=== Flash your ECU ===
Reduce all of your Max WGDC (sometimes called Base WGDC) tables to 50% to prevent overshoot.  Then see a [[How_to_Tune_an_Evo_TB_Alternate|tuning guide]] for how to tune your boost when you are finished with the install.

=== Install the Solenoid ===
Wire orientation should not matter.  Install the resistor in line and solder your connections or create a PNP connector.

=== Tune ===
Then tune, tune, and tune again until your tables are spot on!  Enjoy increased boost holding capacity and control.


Also, when using this method it may be a good idea to raise the values for BCS de-activation RPM.  Stock these are set to 7500.  If you reach 7500 RPM on throttle your WGDC will jump to 100% with these values.  Raise them above your rev-limit to have them continue to interpolate to that RPM.
[[Image:BCS_deactivation_RPM.JPG|center|BCS deactivation RPM]]
Be careful and make sure your XML definitions are correct before modifying this value.  This table is often defined incorrectly.</text>
    <sha1>75b2f71a6acbf6e1910f5bdfaf4fb074f48351e6</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>96530006</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>194</id>
    <parentid>192</parentid>
    <timestamp>2008-10-15T21:57:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add note about broken injector latency table in ecuflash.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="956" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the 96940011 USDM ROM.

==Download==
[[Image:96530006.HEX]]

[[Image:Def file 96530006+tephra510+new tables.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>fdacead281bfb293440704f9efab6257812b9b3b</sha1>
  </revision>
  <revision>
    <id>211</id>
    <parentid>199</parentid>
    <timestamp>2008-10-20T21:10:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add note about immobilizer disabling.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1522" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM.

==96940011 Replacement Notes==

To replace the USDM [[96940011]] ROM with this one (for example, when wanting to use [[TephraMod]] ROMs), you will need to disable the immobilizer; set periphery 0 (FAA), bit 4 to 0 instead of 1.

See also, the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM about the swap.

==Download==
[[Image:96530006.HEX]]

[[Image:Def file 96530006+tephra510+new tables.zip]]

==EcuFlash Definition Errors==

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>c8f7f2ffde14e6917f75b56a68957009e78e3c7e</sha1>
  </revision>
  <revision>
    <id>212</id>
    <parentid>199</parentid>
    <timestamp>2008-10-29T15:19:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>/* EcuFlash Definition Errors */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1522" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM.

==96940011 Replacement Notes==

To replace the USDM [[96940011]] ROM with this one (for example, when wanting to use [[TephraMod]] ROMs), you will need to disable the immobilizer; set periphery 0 (FAA), bit 4 to 0 instead of 1.

See also, the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM about the swap.

==Download==
[[Image:96530006.HEX]]

[[Image:Def file 96530006+tephra510+new tables.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>087c42b25ea244cdba46c30a3699fa6a5cf53a3e</sha1>
  </revision>
  <revision>
    <id>215</id>
    <parentid>214</parentid>
    <timestamp>2008-10-31T12:42:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1528" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM.

==96940011 Replacement Notes==

To replace the USDM [[96940011]] ROM with this one (for example, when wanting to use [[TephraMod]] ROMs), you will need to disable the immobilizer; set periphery 0 (FAA), bit 4 to 0 instead of 1.

See also, the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM about the swap.

==Download==
[[Image:96530006.HEX]]

[[Image:Image:Def_file_96530006_tephra510_new_tables.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>cfa7bcd02800927b7a7298fc26fa64cbfa881e8d</sha1>
  </revision>
  <revision>
    <id>216</id>
    <parentid>214</parentid>
    <timestamp>2008-10-31T12:43:09Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Download */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1522" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM.

==96940011 Replacement Notes==

To replace the USDM [[96940011]] ROM with this one (for example, when wanting to use [[TephraMod]] ROMs), you will need to disable the immobilizer; set periphery 0 (FAA), bit 4 to 0 instead of 1.

See also, the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM about the swap.

==Download==
[[Image:96530006.HEX]]

[[Image:Def_file_96530006_tephra510_new_tables.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>d6be06282e8b6847047a46756cc832b1c96997a3</sha1>
  </revision>
  <revision>
    <id>205</id>
    <parentid>199</parentid>
    <timestamp>2008-11-18T16:46:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2614" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM.

==96940011 Replacement Notes==

The immobilizer functions differently between [[96940011]] and [[96530006]], and you will need to change the behavior for the car to start correctly. You can either [[Immobilizer Disabling|disable the immobilizer]] completely, or change the [[96530006]] immobilizer behavior to function properly with the USDM hardware. ''Only do one, or the other;'' if you disable the immobilizer completely, there is no need to do the following, and if you do the following you should definitely leave the immobilizer enabled for your own security.

To change the behavior, you'll need to add the following to both &lt;tt&gt;96940011.xml&lt;/tt&gt; and &lt;tt&gt;96530006.xml&lt;/tt&gt;:

 &amp;lt;table name="Immobilizer Hex" category="Misc" address="ffa" type="1D" level="2" scaling="Hex16"/&amp;gt;

Then, open your original [[96940011]] ROM, and copy the value from the "Immobilizer Hex" table under the "Misc" section (probably 0x0058). Open your new [[96530006]] ROM, and open the "Immobilizer Hex" table. You'll see that the value is probably 0x004D; paste in the value you copied from your [[96940011]] ROM in its place.

Then, do the same thing for the "Immobilizer" table under the "Misc" section.

At this point, your car should start as expected, with the immobilizer functioning correctly.

For more information on this swap, please read the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM.

==Download==
[[Image:96530006.HEX]]

[[Image:Def_file_96530006_tephra510_new_tables_20081101.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

;2-byte load (no temp compensated)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;OR

;2-byte load  temp compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>1a7edf3aa91c70b24851f83829bb619fc026ac04</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>File:Def file 96530006+tephra510+new tables.zip</title>
  <ns>6</ns>
  <id>144</id>
  <revision>
    <id>619</id>
    <parentid>618</parentid>
    <timestamp>2008-10-31T12:27:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[Image:Def file 96530006+tephra510+new tables.zip]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">Def file 96530006+tephra510+new tables</text>
    <sha1>6701dc24c7f968d1274434e07fa2b8fef0999f35</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>File:96530006+tephra510+new tables.zip</title>
  <ns>6</ns>
  <id>147</id>
  <revision>
    <id>624</id>
    <parentid>623</parentid>
    <timestamp>2008-10-31T12:28:04Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>623</id>
    <timestamp>2008-10-31T12:30:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[Image:96530006+tephra510+new tables.zip]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>625</id>
    <parentid>623</parentid>
    <timestamp>2008-10-31T12:30:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[Image:96530006+tephra510+new tables.zip]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>File:Def file 96530006 tephra510 new tables.zip</title>
  <ns>6</ns>
  <id>148</id>
  <revision>
    <id>628</id>
    <parentid>626</parentid>
    <timestamp>2008-10-31T12:42:28Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>XML definition for 96530006.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">XML definition for 96530006.</text>
    <sha1>7e882d80ae632b39857b6c4bb6c792a8e891b535</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Periphery Configuration</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>633</id>
    <parentid>630</parentid>
    <timestamp>2008-10-31T18:35:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5365" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [EcuFlash] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;Immobilizer Enabled?&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added. That's it!</text>
    <sha1>74bef518ff618fbdf77e395f53c9bdc44f0be099</sha1>
  </revision>
  <revision>
    <id>637</id>
    <parentid>630</parentid>
    <timestamp>2008-10-31T18:37:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5367" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;Immobilizer Enabled?&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added. That's it!</text>
    <sha1>ef62ce959cfc5f62face27e866c17d5aa6097f20</sha1>
  </revision>
  <revision>
    <id>638</id>
    <parentid>630</parentid>
    <timestamp>2008-10-31T18:43:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5878" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;Immobilizer Enabled?&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added.

To change a bit from '''1''' to '''0''', simply select the number, and press the ''['' key. Similarly, to change a '''0''' to a '''1''', select it and press the ']' key. Typing ''='' and entering '''1''' or '''0''' may not work, due to a bug in some versions of EcuFlash.

That's it! Enjoy your new-found control over your ECU, but take care to understand the changes you are making here; you can render your vehicle completely inoperable, or cause a great deal of damage, through misconfiguration of the periphery bits.</text>
    <sha1>f732e7dfe208554f8176e78aacccf9c13fec3775</sha1>
  </revision>
  <revision>
    <id>629</id>
    <timestamp>2008-11-06T00:52:18Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Change lean spool bit from FBA-7 to FBA-0, per http://forums.evolutionm.net/showthread.php?t=375174</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5878" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;Immobilizer Enabled?&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added.

To change a bit from '''1''' to '''0''', simply select the number, and press the ''['' key. Similarly, to change a '''0''' to a '''1''', select it and press the ']' key. Typing ''='' and entering '''1''' or '''0''' may not work, due to a bug in some versions of EcuFlash.

That's it! Enjoy your new-found control over your ECU, but take care to understand the changes you are making here; you can render your vehicle completely inoperable, or cause a great deal of damage, through misconfiguration of the periphery bits.</text>
    <sha1>f422b570b1e346e806c61b73ab9068ba7396ea91</sha1>
  </revision>
  <revision>
    <id>636</id>
    <parentid>630</parentid>
    <timestamp>2008-11-15T18:37:32Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Correct error with immobilizer location.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5878" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;Immobilizer Enabled?&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added.

To change a bit from '''1''' to '''0''', simply select the number, and press the ''['' key. Similarly, to change a '''0''' to a '''1''', select it and press the ']' key. Typing ''='' and entering '''1''' or '''0''' may not work, due to a bug in some versions of EcuFlash.

That's it! Enjoy your new-found control over your ECU, but take care to understand the changes you are making here; you can render your vehicle completely inoperable, or cause a great deal of damage, through misconfiguration of the periphery bits.</text>
    <sha1>d34102f2c21f49bafe64a58b36fb4910fe0ab419</sha1>
  </revision>
  <revision>
    <id>634</id>
    <parentid>630</parentid>
    <timestamp>2009-04-19T17:00:44Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>This is XML, can't have a bare "&lt;" in the text. Also, fix name of periphery 0.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5992" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery0 (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;front o2 sensor heater circuit &lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;timing knockdown on light acceleration &amp;lt; 3000rpm&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;for full time open loop set to 0&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;immobilizer disable&lt;/data&gt;
			&lt;data&gt;rear o2&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;2nd thermo fan table&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added.

To change a bit from '''1''' to '''0''', simply select the number, and press the ''['' key. Similarly, to change a '''0''' to a '''1''', select it and press the ']' key. Typing ''='' and entering '''1''' or '''0''' may not work, due to a bug in some versions of EcuFlash.

That's it! Enjoy your new-found control over your ECU, but take care to understand the changes you are making here; you can render your vehicle completely inoperable, or cause a great deal of damage, through misconfiguration of the periphery bits.</text>
    <sha1>d279e05c8f252e0b05227cdd8a58c4818d450c71</sha1>
  </revision>
  <revision>
    <id>635</id>
    <parentid>630</parentid>
    <timestamp>2009-04-19T17:02:02Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Really fix the "&lt;" this time. (Honestly, might be better to just avoid entirely).</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5996" xml:space="preserve">The Evo ECU has a number of flags, or bits, that control certain behavior of the ECU; everything from disabling certain tests that throw OBD-II codes to changing how the ECU applies timing in certain instances. To access this data, you need to make a few additions to your [[EcuFlash]] configuration.

First, this page assumes you are running EcuFlash version 1.35 or newer; older versions do not have support for bit-level editing directly, and require you to edit these fields much differently.

On windows, assuming your copy of EcuFlash is installed in the default location, run &lt;tt&gt;notepad&lt;/tt&gt;. If you have an Evo VIII or earlier, open the file:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo7base.xml
If you have an Evo XI, however, open:
 C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\evo9base.xml

Once you've opened the file, add the following text, just before the line at the end that says &lt;tt&gt;&lt;/rom&gt;&lt;/tt&gt;:

&lt;pre&gt;	&lt;scaling name="blobbits" storagetype="bloblist" storagebits="1"&gt;
		&lt;data name="0" value="00"/&gt;
		&lt;data name="1" value="01"/&gt;
	&lt;/scaling&gt;

	&lt;table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery0 (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;front o2 sensor heater circuit &lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;Disable EGR / Enabled Ign Adv (set bit=1)&lt;/data&gt;
			&lt;data&gt;timing knockdown on light acceleration &amp;amp;lt; 3000rpm&lt;/data&gt;
			&lt;data&gt;Enable Warmup Ign Retard&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;Enable High Oct Ign Map Lookup (and many other subroutines)&lt;/data&gt;
			&lt;data&gt;"WG solenoid? Enable Speed Limit Test"&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;for full time open loop set to 0&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;immobilizer disable&lt;/data&gt;
			&lt;data&gt;rear o2&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;bit.15&lt;/data&gt;
			&lt;data&gt;bit.14&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;bit.11&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;bit.7&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;2nd thermo fan table&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;Lean Spool&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0443, P0446, P0403, P0243, P0090, P2263&lt;/data&gt;
			&lt;data&gt;P0450, P0451, P0452, P0453 Evap&lt;/data&gt;
			&lt;data&gt;P0441, P0442 Evap&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0031, P0032, P0037, P0038&lt;/data&gt;
			&lt;data&gt;P1400 MAP Sensor&lt;/data&gt;
			&lt;data&gt;P0401 EGR Test&lt;/data&gt;
			&lt;data&gt;P0506, P0507 Idle Test&lt;/data&gt;
			&lt;data&gt;P0170 (P0171, P0172)&lt;/data&gt;
			&lt;data&gt;P0134 Front O2&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.4&lt;/data&gt;
			&lt;data&gt;P0000 - or with bit.5&lt;/data&gt;
			&lt;data&gt;P0132, P0136 O2&lt;/data&gt;
			&lt;data&gt;P0133, P0159&lt;/data&gt;
			&lt;data&gt;P0421 not in FSM&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0128 CT Below Reg&lt;/data&gt;
			&lt;data&gt;P1603 Battery Backup&lt;/data&gt;
			&lt;data&gt;bit.13&lt;/data&gt;
			&lt;data&gt;bit.12&lt;/data&gt;
			&lt;data&gt;P0180 - P0183, P0461, P2066 Fuel Sensors&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;bit.8&lt;/data&gt;
			&lt;data&gt;P0551 PS Pressure&lt;/data&gt;
			&lt;data&gt;P0500 Speed Sens&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;P0234, P0243, P2263&lt;/data&gt;
			&lt;data&gt;P0510 not in FSM&lt;/data&gt;
			&lt;data&gt;P1715, P1750, etc&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;

	&lt;table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits"&gt;
		&lt;table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16"&gt;
			&lt;data&gt;P0140 Rear O2 No Act&lt;/data&gt;
			&lt;data&gt;P0069 MAP vs Baro&lt;/data&gt;
			&lt;data&gt;P0111 IAT Circuit&lt;/data&gt;
			&lt;data&gt;P0554 PS Press Sens&lt;/data&gt;
			&lt;data&gt;P1530 A/C1 Switch&lt;/data&gt;
			&lt;data&gt;bit.10&lt;/data&gt;
			&lt;data&gt;bit.9&lt;/data&gt;
			&lt;data&gt;P0830 Clutch Pedal Circuit&lt;/data&gt;
			&lt;data&gt;P0090 Fuel Pressure Circuit&lt;/data&gt;
			&lt;data&gt;bit.6&lt;/data&gt;
			&lt;data&gt;bit.5&lt;/data&gt;
			&lt;data&gt;bit.4&lt;/data&gt;
			&lt;data&gt;bit.3&lt;/data&gt;
			&lt;data&gt;bit.2&lt;/data&gt;
			&lt;data&gt;bit.1&lt;/data&gt;
			&lt;data&gt;bit.0&lt;/data&gt;
		&lt;/table&gt;
	&lt;/table&gt;&lt;/pre&gt;

Once you have done this, open EcuFlash and load your ROM. You should now see a new section labeled "ECUPeriphery", with the new data you just added.

To change a bit from '''1''' to '''0''', simply select the number, and press the ''['' key. Similarly, to change a '''0''' to a '''1''', select it and press the ']' key. Typing ''='' and entering '''1''' or '''0''' may not work, due to a bug in some versions of EcuFlash.

That's it! Enjoy your new-found control over your ECU, but take care to understand the changes you are making here; you can render your vehicle completely inoperable, or cause a great deal of damage, through misconfiguration of the periphery bits.</text>
    <sha1>420dd5c1e735957f4c603542fd3f26d50fd15fb1</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Immobilizer Disabling</title>
  <ns>0</ns>
  <id>150</id>
  <revision>
    <id>644</id>
    <parentid>643</parentid>
    <timestamp>2008-10-31T18:47:15Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:  * When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; t...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1887" xml:space="preserve">Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:

* When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; the immobilizer code in 96530006 operates differently, and (at least for now) needs to be disabled when used on a USDM vehicle.
* When the original immobilizer code has been lost due to user error, such as overwriting the original ROM on the vehicle with one found online without making a backup first.
* Your keyfob has been damaged, and the RFID tag can no longer be read properly by the ECU.


----
'''This information is provided solely to help you restore the operation of ''your own'' vehicle; this website's operators and authors do not endorse the use of this information for mischief or illegal purposes.'''
----


First, please read the page [[Periphery_Configuration]]; you'll need to add the configuration information shown there to be able to do this.

Once you've added that information, open EcuFlash and load your ROM. Scroll down to the "ECUPeriphery" section, and open the "ECU Periphery 0 (FAA) Bits" table. You should see a table of choices, one of which is "Immobilizer Enabled?", with a "1" in the column next to it. Select the field with "1" in it, and press the "[" key to change it to a "0" instead. You should see the entire bottom half of the column show an indication that it was changed; this is normal, because you're actually changing that whole byte of information, not just the bit you just edited.

After saving your work, simply upload your changes to the ECU as you normally would, and your immobilizer should now be disabled. To test, simply leave your car parked in a bad neighborhood overnight.

'''WARNING''': Be aware that this disables an important security feature of your vehicle, and should not be done without understanding the full impact of the change.</text>
    <sha1>c418f282c04704cacf73246a7dbc68ff6def5e1e</sha1>
  </revision>
  <revision>
    <id>642</id>
    <timestamp>2008-10-31T18:52:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1887" xml:space="preserve">Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:

* When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; the immobilizer code in 96530006 operates differently, and (at least for now) needs to be disabled when used on a USDM vehicle.
* When the original immobilizer code has been lost due to user error, such as overwriting the original ROM on the vehicle with one found online without making a backup first.
* Your keyfob has been damaged, and the RFID tag can no longer be read properly by the ECU.


----
'''This information is provided solely to help you restore the operation of ''your own'' vehicle; this website's operators and authors do not endorse the use of this information for mischief or illegal purposes.'''
----


First, please read the page [[Periphery Configuration]]; you'll need to add the configuration information shown there to be able to do this.

Once you've added that information, open EcuFlash and load your ROM. Scroll down to the "ECUPeriphery" section, and open the "ECU Periphery 0 (FAA) Bits" table. You should see a table of choices, one of which is "Immobilizer Enabled?", with a "1" in the column next to it. Select the field with "1" in it, and press the "[" key to change it to a "0" instead. You should see the entire bottom half of the column show an indication that it was changed; this is normal, because you're actually changing that whole byte of information, not just the bit you just edited.

After saving your work, simply upload your changes to the ECU as you normally would, and your immobilizer should now be disabled. To test, simply leave your car parked in a bad neighborhood overnight.

'''WARNING''': Be aware that this disables an important security feature of your vehicle, and should not be done without understanding the full impact of the change.</text>
    <sha1>3e42a5a6d97b188639b7f47f13244d48dfdb456c</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Patching</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>334</id>
    <parentid>329</parentid>
    <timestamp>2008-10-31T18:50:00Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add periphery configuration and immobilizer disabling pages.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7484" xml:space="preserve">==Individual ROMs==
Please see [[:Category:ROMs]] for our master list of information on specific ROMs.

==Tephra Mods==
[http://forums.evolutionm.net/member.php?u=62041 tephra], a member of [[EvolutionM]] hailing from Melbourne, Australia has made some enormous contributions to stock ECU tuning.  Find out more about [[TephraMod]]

== Pre-Patched ROMs ==
[[88590015_Patched_Mods]]

==Misc Mods==
===Removing pin from Evo IX ECU===
[http://forums.evolutionm.net/showthread.php?t=337757 Guide by Mr Fred]
===MUT Table Definitions===
[http://forums.evolutionm.net/showthread.php?t=337811 Here] by Mr Fred

[[AddMutTableToEcuFlash|Mut table definition for ecuflash]]
===[[Periphery Configuration]]===
See [[Periphery Configuration]] for information on viewing and changing the ECU periphery bit configuration.

===[[Immobilizer Disabling]]===
Read [[Immobilizer Disabling]] if your car cannot be started because of the immobilizer.

===[[Glossary | AIT]] logging through ECU===
[http://forums.evolutionm.net/showthread.php?t=341606 Original thread here]

This patch allows the ECU to read manifold air temperature on USDM Evos.  This is done by feeding the output from a GM IAT sensor into the ECU’s ADC input for monitoring fuel temperature.  Fuel temperature is monitored only for emissions performance. It is not used to control emissions equipment. The patch includes code to simulate the fuel temperature.  The car will pass emissions with this setup.

Hardware needed will be a GM IAT sensor, NPT fitting, a sensor wiring pigtail, and a pin for your ECU. Total cost for hardware is around $60. Weld the NPT fitting to one of your UICPs. One wire from the sensor will need to go to the fuel temperature signal input on the ECU. The other wire goes to ground (bolt it to the engine block).

Manifold air temperature measurement can be very handy for several reasons:

1) Finally a good way to monitor MAT for speed density. Its better than highjacking the IAT sensor input because the IAT sensor is used to control quite a few things in the ECU. By using the fuel temperature ADC input, the IAT sensor can be kept intact and working.

2) Good for monitoring turbo performance. We can finally see how hot the air is getting from the stock turbo at 7500 rpm after the turbo and IC.

3) Good for testing intercooler performance. We finally have a tool that allows us to easily measure the effect of an aftermarket IC on intake air temperature at the manifold.

===Cold start enrichment===
[http://forums.evolutionm.net/showthread.php?t=347668 Original thread here]

This modification uncovers two tables that deal with fuel enrichment during cranking.  The tables are Startup Enrichment IPW Adder #1 and Startup Enrichment IPW Adder #1
Both tables are used only when the engine speed is less than 438 rpm. Table #2 applies when the coolant temp is greater than 419°F (absolutely never), and table #1 applies when the coolant temp is less than 419°F (always the case). The scaling is chosen so that the tables have the same time units as the injector latency vs battery voltage table.

The ECU values and the three observed values are shown in the table below. The observed values are dead on with the table values. This suggests that this table is the main table for startup enrichment for Evo 9s and that these other tables found in older ROMs are probably not in the Evo 9 ROM. 

{|border="1" colspan="3"|
|+ECU Setting
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| -32 || -26 || 226.3
|-
| -18 ||   0 || 108.1
|-
|  -8 ||  18 ||  46.1
|-
|   7 ||  45 ||  17.3
|-
|  20 ||  68 ||  15.4
|-
|  34 ||  93 ||  12.4
|-
|  50 || 122 ||   6.7
|-
|  77 || 171 ||   3.0
|-
|  82 || 180 ||   3.0
|}

{|border="1" colspan="3"|
|+Observed
|-
!Coolant Temp (C)
!Coolant Temp (F)
!Startup IPW Adder (ms)
|-
| 30 ||  86 || 13.6
|-
| 50 || 122 ||  6.4
|-
| 83 || 181 ||  3.3
|}

===MUT and 2-Byte===

* [[Add_MUT_Table_To_EcuFlash|Add the MUT table to EcuFlash]]
* [http://forums.evolutionm.net/showthread.php?t=337811 MUT table definitions thread] on [[EvolutionM]]

===2-Byte Logging===
* [[2-Byte_Logging|Add 2-byte logging to your ROM]]
* [http://forums.evolutionm.net/showthread.php?t=327185 2-Byte load, RPM, and airflow thread] on [[EvolutionM]]

===Lean Spool===
* [http://forums.evolutionm.net/showthread.php?t=261465 Disable lean spool on Evo IX]

==Boost Control Mods==
===Log boost with JDM MAP sensor===
http://forums.evolutionm.net/showthread.php?t=259595

===Improved load based boost control===
http://forums.evolutionm.net/showthread.php?t=288408

===Direct Boost Control (PSI)===
How-To by Mr Fred [http://forums.evolutionm.net/showthread.php?t=293981 here]

===Additional boost tables===
http://forums.evolutionm.net/showthread.php?t=333479

===3 Port Boost Control===
[[3_Port_Boost_Control]] using one of many aftermarket solenoids

==02 Sensor Mods==
===Log wideband AFR through ECU(rear 02 sim)===
[http://forums.evolutionm.net/showthread.php?t=337823 Original thread here]
Most wideband meters include both a serial output and a 0-5V analog output. The serial out is meant to be connected directly to a computer while the analog out was designed to be fed into an ECU.  This method feeds the analog output data into the rear O2 ADC input on the ECU.

Before getting started, be sure that you have a few female ECU pins handy. The pins for Evo 8s are widely available. Jack_of_Trades has posted the part number on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page]. (You'll need to scroll down a little ways to find the pin part number.) Jack_of_Trades has the only pins available pretty much across the entire world for the Evo 9. You can get the pins from him [http://forums.evolutionm.net/showthread.php?t=341523 here].

Hardware Modifications

1) Install the wideband if it is not already installed. Proper grounding is key for accurate AFR readings when using the analog output. Fortunately, proper grounding is pretty easily accomplished on the Evo because the ECU is grounded to multiple locations on the car. The ECU is grounded directly to the driveshaft tunnel just in front and to the right of the shifter assembly. There is a bolt about 5 inches in front of that bolt that attaches the airbag electronics tray to the chassis. The heater ground wire can be installed there. I grounded the analog output ground and system ground separately by drilling a hole into the chassis about two inches below the bolt for the heater ground. Sand off the paint on the chassis before attaching the ground wire lugs.

2) Find the rear O2 pin on your ECU harness, remove it, and tape it back out of the way. Jack_of_Trades has instructions on this [http://www.dsm-ezine.com/evoVIII_adc_switch.html page] (again scroll down) on how to do the removal and install for the Evo 8. Instructions for the Evo 9 are [http://forums.evolutionm.net/showthread.php?p=5518639 here]. Pinout diagram for the USDM Evo 8 is [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm here]. The diagram for the Evo 9 is [http://forums.evolutionm.net/showthread.php?t=313670 here].

3) Attach the female ECU pin to the analog output wire. I strongly suggest soldering and crimping the wire to the pin. Soldering helps insure that the wire will not accidentally be pulled from the pin while its in the ECU plug.

4) Install the pin into the plug.

===Front &amp; rear 02 sim (control closed loop with wideband)===
http://forums.evolutionm.net/showthread.php?t=360398</text>
    <sha1>1a190d2a7f4795017ed971ba87c44cb5b59a1ff3</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Development Tips</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>681</id>
    <parentid>680</parentid>
    <timestamp>2008-11-25T22:09:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3149" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

If you only read one document about the Evo ECU hardware platform, read this one:

http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

That is the original [http://www.renesas.com/ Renesas] hardware manual for the SH-2 platform.

For looking up additional information, you should be aware that both the Evo VIII and IX use an SH2E processor; the Evo VIII uses an SH7052F platform, and the IX uses an SH7058F. One of the primary differences is that the Evo VIII has a 256KB ROM image, while the IX has a 512KB ROM.</text>
    <sha1>0ec50e1f4b96bcdea402553636f8ce637dc04ceb</sha1>
  </revision>
  <revision>
    <id>679</id>
    <parentid>678</parentid>
    <timestamp>2008-11-25T23:11:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3351" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

If you only read one document about the Evo ECU hardware platform, read this one:

http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

That is the original [http://www.renesas.com/ Renesas] hardware manual for the SH-2 platform.

For looking up additional information, you should be aware that both the Evo VIII and IX use an SH2E processor; the Evo VIII uses an SH7052F platform, and the IX uses an SH7058F. One of the primary differences is that the Evo VIII has a 256KB ROM image, while the IX has a 512KB ROM.</text>
    <sha1>0798420fad31117cab90edf9ea683e30bceca0b3</sha1>
  </revision>
  <revision>
    <id>683</id>
    <parentid>680</parentid>
    <timestamp>2009-03-13T14:12:43Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3673" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

If you only read one document about the Evo ECU hardware platform, read this one:

http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

That is the original [http://www.renesas.com/ Renesas] hardware manual for the SH-2 platform.

For looking up additional information, you should be aware that both the Evo VIII and IX use an SH2E processor; the Evo VIII uses an SH7052F platform, and the IX uses an SH7058F. One of the primary differences is that the Evo VIII has a 256KB ROM image, while the IX has a 512KB ROM.

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.</text>
    <sha1>a5ae204fd3dd3aae33259b53aa5db1e92da5123e</sha1>
  </revision>
  <revision>
    <id>677</id>
    <timestamp>2009-07-08T19:12:30Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Correct some mis-information about the IX ECU (it's a 7055, not a 7058).</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3781" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

If you only read one document about the Evo ECU hardware platform, read this one:

http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

That is the original [http://www.renesas.com/ Renesas] hardware manual for the SH-2 platform.

For looking up additional information, you should be aware that both the Evo VIII and IX use an SH-2e processor; the Evo VIII uses an SH7052F platform, and the IX uses an SH7055F. The primary difference is that the Evo VIII ECU (SH7052F) has a 256KB ROM image and 12KB of RAM, while the IX ECU (SH7055F) has a 512KB ROM image and 32KB of RAM; otherwise, the hardware is essentially the same.

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.</text>
    <sha1>28484467c02dcec37ee2e0a87482b0eb66a0f172</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>ECU Development</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>668</id>
    <parentid>667</parentid>
    <timestamp>2008-11-25T22:10:54Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="278" xml:space="preserve">This page is for sharing new findings in the stock ECU.  New tables, routines, etc...

=Getting Started=

See our new [[Development Tips]] page!

=New table/map discussions=

==Cold Start Fueling==
Cold Start Fueling Info Here

==Cold Start Timing==

Cold Start Timing Info Here</text>
    <sha1>4b0b753a66d4c442725a7fc1f7f2b9843f8bcf74</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>IDA Pro</title>
  <ns>0</ns>
  <id>159</id>
  <revision>
    <id>684</id>
    <timestamp>2008-11-25T22:12:32Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: IDA stands for Interactive Disassmbler, and is shorthand for the product called [http://www.hex-rays.com/idapro/ IDA Pro], produced by a company named [http://www.hex-rays.com/ Hex-Rays].</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="187" xml:space="preserve">IDA stands for Interactive Disassmbler, and is shorthand for the product called [http://www.hex-rays.com/idapro/ IDA Pro], produced by a company named [http://www.hex-rays.com/ Hex-Rays].</text>
    <sha1>c88ad84137ad927798add21781302b71a30862cd</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Downloads</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>358</id>
    <parentid>357</parentid>
    <timestamp>2008-11-25T22:18:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Download Section */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1080" xml:space="preserve">==Download Section==
Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]
===Unknown Evo VII ([[93390000]])===
===03-05 JDM VIII (96260009)===
===03-05 JDM RA ([[90550001]])===
===03-04 USDM VIII ([[94170015]])===
===05 USDM VIII ([[96940011]])===
===05 EDM VIII ([[96530006]]) Replacement for USDM '05 VIII===
===06 USDM IX ([[88590015]])===
===06 USDM IX MR (Mexican market) - (88840016)===
===06 AUDM IX (88580014)===
===06 EUDM IX (88840017)===</text>
    <sha1>00798960b14889315423cbb6aa40fc3564969c19</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Links</title>
  <ns>8</ns>
  <id>66</id>
  <revision>
    <id>237</id>
    <parentid>235</parentid>
    <timestamp>2008-11-25T22:20:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">Helpful Links
For Developers</text>
    <sha1>0a4316fad13cb69d52399747045000db8bacedc9</sha1>
  </revision>
  <revision>
    <id>235</id>
    <timestamp>2008-11-25T22:20:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">Helpful Links</text>
    <sha1>178674ddef1d1ceced9b221f91dff91c0e5b301a</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Links-url</title>
  <ns>8</ns>
  <id>65</id>
  <revision>
    <id>231</id>
    <timestamp>2008-11-25T22:20:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="29" xml:space="preserve">Helpful_Links
ECU_Development</text>
    <sha1>c528b30ec0f0193e914912ad7f9f5789e2f61456</sha1>
  </revision>
  <revision>
    <id>232</id>
    <parentid>231</parentid>
    <timestamp>2008-11-25T22:20:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">Helpful_Links</text>
    <sha1>2154db8952b674280fc5d96a2e8b8a8d84b0c078</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>64</id>
  <revision>
    <id>229</id>
    <parentid>223</parentid>
    <timestamp>2008-11-25T22:21:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="197" xml:space="preserve">* navigation
** mainpage|mainpage
** links-url|links
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
** developers-url|developers</text>
    <sha1>dac0f6ff40204122a8b1980ec11874949c40bc09</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Developers</title>
  <ns>8</ns>
  <id>160</id>
  <revision>
    <id>688</id>
    <parentid>685</parentid>
    <timestamp>2008-11-25T22:21:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: For developers</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14" xml:space="preserve">For developers</text>
    <sha1>f18d0d18586127e1f56da0a611a7144770659f55</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Developers-url</title>
  <ns>8</ns>
  <id>161</id>
  <revision>
    <id>689</id>
    <timestamp>2008-11-25T22:22:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: ECU_Development</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">ECU_Development</text>
    <sha1>a8315191432bdaefedec5d7a3918d3e08585a48f</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Booksources</title>
  <ns>8</ns>
  <id>162</id>
  <revision>
    <id>690</id>
    <timestamp>2008-11-25T23:05:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: Book sources  [http://www.amazon.com/gp/product/MAGICNUMBER?ie=UTF8&amp;tag=edwardsmarsha&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1593271786 Find this book] at [http://www.amazon.c...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="200" xml:space="preserve">Book sources

[http://www.amazon.com/gp/product/MAGICNUMBER?ie=UTF8&amp;tag=edwardsmarsha&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1593271786 Find this book] at [http://www.amazon.com/ Amazon].</text>
    <sha1>bcf35a309abea8673fd0ec04a2099765da3d1dd2</sha1>
  </revision>
  <revision>
    <id>691</id>
    <parentid>690</parentid>
    <timestamp>2008-11-25T23:05:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Replacing page with 'Book sources'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">Book sources</text>
    <sha1>06c51f428e737889404ce16d19a7bcf8e061b5ac</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>EvoEcu:Book sources</title>
  <ns>4</ns>
  <id>163</id>
  <revision>
    <id>693</id>
    <parentid>692</parentid>
    <timestamp>2008-11-25T23:10:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: [http://www.amazon.com/gp/product/MAGICNUMBER?ie=UTF8&amp;tag=edwardsmarsha&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1593271786 Find this book] at [http://www.amazon.com/ Amazon].</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="186" xml:space="preserve">[http://www.amazon.com/gp/product/MAGICNUMBER?ie=UTF8&amp;tag=edwardsmarsha&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1593271786 Find this book] at [http://www.amazon.com/ Amazon].</text>
    <sha1>5d70cad92ecc9ff153948ae5ae021aba84edccf7</sha1>
  </revision>
  <revision>
    <id>694</id>
    <parentid>692</parentid>
    <timestamp>2008-11-26T02:47:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[EvoEcu:Book sources]]" [edit=sysop:move=sysop]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="186" xml:space="preserve">[http://www.amazon.com/gp/product/MAGICNUMBER?ie=UTF8&amp;tag=edwardsmarsha&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1593271786 Find this book] at [http://www.amazon.com/ Amazon].</text>
    <sha1>5d70cad92ecc9ff153948ae5ae021aba84edccf7</sha1>
  </revision>
  <revision>
    <id>692</id>
    <timestamp>2008-11-26T15:09:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">[http://www.amazon.com/exec/obidos/ASIN/MAGICNUMBER/edwardsmarsha/ Find this book] at [http://www.amazon.com/ Amazon.com]!</text>
    <sha1>a56470893b474a4411aac010c6d74f3c3c859538</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Helppage</title>
  <ns>8</ns>
  <id>212</id>
  <revision>
    <id>792</id>
    <timestamp>2008-12-05T19:52:23Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: metawikipedia:Help:Contents</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">metawikipedia:Help:Contents</text>
    <sha1>1ab9b963038e1985e2b6a998569698f201c761ec</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MediaWiki:Edithelppage</title>
  <ns>8</ns>
  <id>213</id>
  <revision>
    <id>793</id>
    <timestamp>2008-12-05T19:53:04Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>New page: metawikipedia:Help:Editing</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">metawikipedia:Help:Editing</text>
    <sha1>6f750a043c83fcb2ee03a2ed7a9da73812313eb1</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>96260009</title>
  <ns>0</ns>
  <id>187</id>
  <revision>
    <id>743</id>
    <parentid>742</parentid>
    <timestamp>2009-03-26T23:57:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="445" xml:space="preserve">==Information==
Car:  Mitsubishi Lancer Evolution 8

Year: 2003-2005

Market: JDM

Case id:

==Replacements==

==Download files==
[[Image:96260009_EVO8_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|96260009]]</text>
    <sha1>e697dd94b36b2b43e49efe5d8964bb5d4371b4c9</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>40</id>
    <parentid>1</parentid>
    <timestamp>2009-04-02T21:18:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>add link to dev tips page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2459" xml:space="preserve">'''I ask that anyone who is going to edit or add to the wiki please browse through it thoroughly before adding content.  I have noticed that as the wiki is expanding we seem to be duplicating content.  For example we already have a page on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]],[[Glossary]] etc..  If you want to discuss these items please simply link to their wiki page and possibly add content there if needed.  We don't need to have several pages all talking about EvoScan for example.  THANKS FOR YOUR HELP'''


The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

==Warning==
Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Glossary==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
Be sure to check out the [[Development_Tips]] page if you're interested in getting started with Evo ECU development!</text>
    <sha1>a32d44d3195f87cca70b62e0f3b21539c3dea820</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>TephraMod</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>436</id>
    <parentid>433</parentid>
    <timestamp>2009-05-04T18:43:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>/* Version 7 changes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14995" xml:space="preserve">--under construction-- please edit/fix ANY mistakes you see below!!!

This page will list out the various MOD's included in the TephraMOD patch package:

We have tried as hard has possible to keep MOD's between different ROMID's as consistant as possible, and currently there are TWO streams - EVO's WITH the "Intercooler Spray System" and those WITHOUT:

== Background &amp; Overview ==
The Tephra Mods are developed by a great Australian with the forum nickname "Tephra".  The basis for these mods were a few simple modifications that had to be ported to a ROM by each individual user.  Around the time when map switching was coming around it was determined that it would be easier to distribute a ROM to use as an actual base, and allow the user to copy their specific maps and changes into the upgraded ROM.&lt;br&gt;
&lt;br&gt;
Thus the Tephra ROM was born.  This began at "version 5".  So far there have also been version 5.10, v6 (mostly testing for V7), and V7.  Each version adds new features and fixes others.  Mods by other modders are often made compatible with these roms because they offer such a good feature base.&lt;br&gt;
&lt;br&gt;
A map switching harness is not required to use the Tephra ROM, but is required if you desire to use the map switching feature and do not have an ICS switch.  It is possible to use a switching harness with an ICS, and also to build a customer harness using a master on/off from something like an Aquamist injection kit to control the map switching.  Harnesses are sold by Jack_of_Trades, but he also provides schematics to create your own.&lt;br&gt;
&lt;br&gt;
Please note that not all features may be available in your Tephra Rom Version.  Generally features are available in every version, but some may be dropped if they are deemed wasteful or unneeded.
&lt;br&gt;
&lt;br&gt;

== Version 7 changes ==
* Cranking Enrichment addition to "altmaps"
* Boost Drop for High knock
* AFR safety CEL Flash
* AFR safety boost drop
* Launch Map mode
** uses TPS + SPEED to impose a different fuel+timing map
* Altmap toggle by TPS (like Valet, CANNOT be used with Valet)
* Airflow calcs
* TPS+IAT corrections for boost maps
* 3d boost maps with gear/rpm axis's

= Main Tephra Mod Options Table =
=== Valet Mode ===
Allows you to enable a "Valet" mode thereby disabling some features to prevent unintended "hoonage" by valets, friends, theives, etc.  When enabled valet mode can be activated or deactivated by turning the key to the 'ON' position without starting the car and pressing the gas pedal for the time specified in the 'Valet Rev Limit Time to Activate' table of the Tephra Mods section.  The CEL will then flash for the amount of time specified in 'Valet Rev Limit Flash Time' table.  It will also flash when the car is started.  When enabled RPM will be limited to the value specified in the 'Valet Rev Limit' table ('''Note:''' if this is too low your car will not be able to idle properly and will shut off).  As of V7 WGDC should also be set to 0% while in valet mode. &lt;br&gt;
'''Enable Valet Mode'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Valet mode in the ROM:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Auto-Valet on Fresh Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Auto-Valet mode in the ROM.  This will enable valet mode each time the car is shut off unless you follow the proceadure to disable it:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
=== Other Options ===
Enable Alternate Maps Master ADC0F=1, AutoICS=2 &lt;br&gt;
'''Enable Alternate Maps Master ADC0F=1, AutoICS=2''' &lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Alt Maps in the ROM:
::* 0 = Disabled
::* 1 = Enabled - Switched via Map switch into ADC0F pin of ECU
::* 2 = Enabled - Switched via ICS Switch
&lt;br&gt;
'''Restore ICS State Fresh Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable restoring the state of the ICS setting which would normally default to off every time the car was started:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Flash ICS when on Alternate Map'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable forcing the ICS light to flash when you are in alternate map mode:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Flash CEL on Knock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable Flashing the 'Check Engine' light when a knock value exceeds the value in the 'KnockSum Required for Slow CEL (Low Knock)' table in the Tephra Mods section.  If you exceed the value set in the 'KnockSum Required for Fast CEL (High Knock)' table the light will flash twice as fast.  You must exceed the value set in 'Load Required for CEL on Knock' for the flash to occur.  The light will flash for the time set in 'CEL on Knock Flash Time' (set in milliseconds):
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Drop boost on High-Knock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to set WGDC to 0% if you exceed the value set in the 'KnockSum Required for Fast CEL (High Knock)' table.  The WGDC will remain at 0% for the amount of time specified in the 'High Knock Boost Drop Time' table:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Manual ICS Linger'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable... NEED MORE INFO:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Spray ICS on Kock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to trigger the ICS on a set knock point (or any knock?):
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable No Lift to Shift'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for NLTS in the ROM:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Rear O2 Simulator'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to help prevent a CEL for users with a high flow catalytic converter.  It will simulate the rear O2 signal based off of the front O2 signal to help prevent catalytic efficiency check errors:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable MAP Averaging'''&lt;br&gt;
: For users who have direct boost control this helps to stabilize the boost that is "seen" by the ECU via the JDM MAP (or whatever is on that channel).  Rather than reporting the most recent reading, the ECU will see a running average of the most recent 3 MAP values.  It is calculated as 
&lt;pre&gt;[n-2 sample average] + [n-1 sample] + [n sample]&lt;/pre&gt;
::* 0 = Disabled
::* 1 = Enabled
: Note:  Setting this will reflect the updated averaged value when logging the default MUT Item for boost.  A value can be set at another location to log *actual* boost.
&lt;br&gt;
'''Enable Manifold Temperature'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable MAT logging via temperature sensor input in the Manifold when disabling the fuel temperature sensor.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable WBO2 Check AFR Safety'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable a CEL Flash when AFR is out of range.  You must have an analog wideband signal wired into your rear O2 ADC input for this to function.  You must exceed the value in the AFR Safety Load Threshold table and then have the input voltage from the wideband out of the range set in the 'AFR Safety Min AFR' and 'AFR safety Max AFR' tables.  When enabled the CEL will flash for the amount of time specified in the 'AFR Safety Boost Drop Time and Flash Time' table.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Drop Boost on AFR out of Range'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable a boost drop via 0% WGDC when the conditions for 'Enable WBO2 Check AFR Safety' are met.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;&lt;br&gt;

= Detailed Options =
== NLTS - No Lift to Shift ==
No Lift to Shift or NLTS allows the driver to keep the car at WOT whilst shifting - this has a number of advantages:&lt;br&gt;
* Boost that is built up isn't lost when the TPS is slammed shut and the BOV is activated&lt;br&gt;
* When done correctly a NLTS WOT Shift should do less damage to the driveline than a normal WOT Shift&lt;br&gt;
&lt;br&gt;
Tephra's implementation of NLTS is very simple, when the preset conditions (Load/TPS/Speed/Clutch Down) are met&lt;br&gt;
the ECU "remembers" what RPM you shifted at and imposes a temporary rev limiter at that RPM - the configurable "RPM Drop".&lt;br&gt;
&lt;br&gt;
eg - If your RPM Drop parameter is 1500 and you shift at 7500RPM, then a rev limiter (like the normal 7606 RPM rev&lt;br&gt;
limiter) will be imposed at 6000RPM, this means whilst you are shifting AND the RPM are higher than 6000RPM the&lt;br&gt;
engine is experiencing FUEL CUT.&lt;br&gt;
&lt;br&gt;
Once you get off the clutch pedal the normal rev limiter (7606RPM by default) is re-imposed.&lt;br&gt;
&lt;br&gt;
=== Problems with NLTS ===
Because we are using the TOP CLUTCH SWITCH some people find they are enabling NLTS by accident as the clutch&lt;br&gt;
pedal doesn't need to travel very far to de-activate this switch. ALSO Make sure you fully come of the clutch pedal&lt;br&gt;
otherwise the rev limiter will still be imposed.&lt;br&gt;
Alternatively you can put some foam on the clutch pedal (where the switch contacts) to lengthen the travel of the clutch&lt;br&gt;
pedal allowed before switch de-activates.

[[Image:Nlts-settings.png]]
=== NLTS Settings ===
'''Enable No Lift to Shift'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for NLTS in the ROM:
::* 0 = Disabled
::* 1 = Enabled
: In the above image it is set to 0, thus NLTS is disabled and the other NLTS settings are irrelevant.&lt;br&gt;&lt;br&gt;
'''NLTS TPS Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0% to 100%
: In the above image it is set to 98%, meaning once all the other conditions are met NLTS will impose the rev limiter once the TPS is over 98%&lt;br&gt;&lt;br&gt;
'''NLTS Load Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0% to 400%
: In the above image it is set to 150%, meaning once all the other conditions are met NLTS will impose the rev limiter once the Load exceeds 150%&lt;br&gt;
: (NOTE: This condition isn't used for disabling the rev limiter because Load drops when the NLTS rev limiter is engaged)&lt;br&gt;&lt;br&gt;
'''NLTS Speed Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0km/h to 250km/h
: In the above image it is set to 30km/h, meaning once all the other conditions are met NLTS will impose the rev limiter once the Speed exceeds 30km/h&lt;br&gt;
: (NOTE: This condition allows the driver to slip the clutch on launch, without it you may hit NLTS on launch which would be bad)&lt;br&gt;&lt;br&gt;
'''NLTS RPM Drop:'''&lt;br&gt;
: This setting is found in the "Mods" group - Essentially it tells the ECU what at RPM to impose the rev limiter:
::* 0rpm to 3000rpm
: In the above image it is set to 800rpm, meaning once all the conditions are met NLTS will impose the rev limiter at the CURRENT RPM - RPM Drop&lt;br&gt;
: ie if you shift at 6500RPM then the rev limiter would be set to 5700RPM&lt;br&gt;&lt;br&gt;

== Intercooler Spray (ICS) Mods ==


[[Image:Ics-settings.PNG]]

=== ICS Settings ===
'''Restore ICS State on Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, when enabled the ICS system state (little green lamp) will be restored:
::* 0 = Disabled - ie don't restore the ICS Auto State on Fresh Ignition
::* 1 = Enabled - ie restore the ICS Auto State on Fresh Ignition
: In the above image it is set to 1, thus when the car is first turned on it will restore the same state that the car was in before it was turned off last.&lt;br&gt;&lt;br&gt;
'''Enable Manual ICS Linger:'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, on a stock Evo pressing the Manual ICS button will spray for the duration of the press, this modification causes the spray to keep going for as long as you have configured.
::* 0 = Disabled - ie don't cause the manual ICS button to keep spraying
::* 1 = Enabled - ie cause the manual ICS button to keep spraying
&lt;br&gt;
'''Manual ICS Linger Time'''&lt;br&gt;
: This setting is found in the "Mods" group, it specifies how long to spray after the Manual button has been released:
::* 0ms to 5000ms 
: In the above image it is set to 1500ms, thus when the manual ICS button is pressed and released the ICS will spray for 1.5 seconds longer.&lt;br&gt;&lt;br&gt;
'''Enable Spray ICS on Knock:'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table
::* 0 = Disabled - ie default evo behaviour
::* 1 = Enabled - ie when enabled (and on AutoICS) this will cause the ICS system to spray once the other conditions have been met.
&lt;br&gt;

==Alt Maps==
integrated with Aquamist HFS-1, GM BCS, and direct boost control mod [http://forums.evolutionm.net/showthread.php?t=334575 here] and [http://www.youtube.com/watch?v=dWUNj-s3GBE video here]

====Checking Switch Functionality and Logging Alt Map status====
To log and verify that your alt-map switch is functioning properly make a copy of your map and change [[Add_MUT_Table_To_EcuFlash|MUT]] values to log 0x6B0D (Voltage in bits) and 0x8425 (altmaps: 0-normal, 3-alt (4-alt in 88590015)).

For example, you can temporarily set:
{|border="1" cellpadding="5" cellspacing="0"
|MUT00:
|0x8425
|-
|MUT83:
|0x6B0D
|}
&lt;br&gt;
Then, to log in [[EvoScan]] add these definitions:
{|border="1" cellspacing="0"
|&lt;nowiki&gt;&lt;DataListItem DataLog="N" Color="" Display="ALT MAP Activation" LogReference="AltMapActive" RequestID="00" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="5" ChartMin="0" ChartMax="5" ScalingFactor="1" Notes="Alt Map Activation. 0= Standard Maps 3= Alt Maps" Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;&lt;DataListItem DataLog="N" Color="" Display="ALT Map Input Voltage" LogReference="AltMapVoltage" RequestID="83" Eval="x*5/255" Unit="Vdc" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="5" GaugeMax="15" ChartMin="0" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|}
&lt;br&gt;
Or MitsuLogger with these defs:
{|border="1" cellspacing="0"
|&lt;nowiki&gt;&lt;Request LogReference="AltMapActive" RequestID="00" Eval="x" Unit="unit" Logged="y" Response="1"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;&lt;Request LogReference="AltMapVoltage" RequestID="83" Eval="x*5/255" Unit="Vdc" Logged="y" Response="1"/&gt;&lt;/nowiki&gt;
|}
&lt;br&gt;
After you see that your switch is working properly, your voltage is &lt;5V (Ideally it should be &lt;4.7V), and your alt-maps are being activated you should switch back to the map without the modified MUT00.  You can also remove the info from your [[Evoscan]]/Mitsulogger XML.</text>
    <sha1>602ed9bb61866cbca1a19a9ceaf1526c092ffcb6</sha1>
  </revision>
</page>
<page arvcontinue="20080813215714|604">
  <title>MUT Requests</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>809</id>
    <parentid>808</parentid>
    <timestamp>2009-05-18T14:29:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Fo...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3031" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.

{|
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|(x-128)/5
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|-
|13
|
|O2Sensor
|Oxygen Sensor
|V
|0.01952*x
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|-
|1A
|
|AirFlow
|Air Flow
|Hz
|6.25*x
|-
|1C
|
|Load
|Load
|load
|5*x/8
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment
|airflow/rev
|200*x/255
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|-
|2C
|
|AirVol
|Air Volume
|
|x
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|-
|3C
|
|O2Sensor2
|Oxygen Sensor #2
|V
|0.01952*x
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|-
|4A
|
|CrankSignalSw
|Crank Signal
|On/Off
|x bit 64
|-
|4A
|
|IdlePosSw
|Idle Position Switch
|On/Off
|x bit 128
|-
|4A
|
|PwrSteeringSw
|Power Steering Switch
|On/Off
|x bit 8
|-
|4A
|
|ACSwitch
|Air Conditioning Switch
|On/Off
|x bit 16
|-
|4A
|
|InhibitorSw
|Inhibitor Switch
|Flag
|x bit 32
|-
|6A
|
|knock_adc
|knock_adc_processed
|count
|x
|-
|6B
|
|knock_base
|knock_base
|count
|x
|-
|6C
|
|knock_var
|knock_var
|count
|x
|-
|6D
|
|knock_change
|knock_change
|count
|x
|-
|6E
|
|knock_dynamics
|knock_dynamics
|count
|x
|-
|6F
|
|knock_flag
|knock_flag
|count
|x
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|-
|8A
|
|LoadError
|Load Error
|load
|0.15625*x-20
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|}</text>
    <sha1>d3daeea9801c036924fb1ac30386a8b3db40556f</sha1>
  </revision>
  <revision>
    <id>807</id>
    <parentid>803</parentid>
    <timestamp>2009-05-19T00:58:40Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>MUT 4A is purge control duty cycle, not a bunch of bits</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2793" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.

{|
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|(x-128)/5
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|-
|13
|
|O2Sensor
|Oxygen Sensor
|V
|0.01952*x
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|-
|1A
|
|AirFlow
|Air Flow
|Hz
|6.25*x
|-
|1C
|
|Load
|Load
|load
|5*x/8
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment
|airflow/rev
|200*x/255
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|-
|2C
|
|AirVol
|Air Volume
|
|x
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|-
|3C
|
|O2Sensor2
|Oxygen Sensor #2
|V
|0.01952*x
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|-
|6A
|
|knock_adc
|knock_adc_processed
|count
|x
|-
|6B
|
|knock_base
|knock_base
|count
|x
|-
|6C
|
|knock_var
|knock_var
|count
|x
|-
|6D
|
|knock_change
|knock_change
|count
|x
|-
|6E
|
|knock_dynamics
|knock_dynamics
|count
|x
|-
|6F
|
|knock_flag
|knock_flag
|count
|x
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|-
|8A
|
|LoadError
|Load Error
|load
|0.15625*x-20
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|}</text>
    <sha1>6fc297338a3955c66c8bd2fe9ee8efb9d6922666</sha1>
  </revision>
  <revision>
    <id>806</id>
    <parentid>803</parentid>
    <timestamp>2009-05-19T01:05:30Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add MUT 54 and 55.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2950" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.

{|
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|(x-128)/5
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|-
|13
|
|O2Sensor
|Oxygen Sensor
|V
|0.01952*x
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|-
|1A
|
|AirFlow
|Air Flow
|Hz
|6.25*x
|-
|1C
|
|Load
|Load
|load
|5*x/8
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment
|airflow/rev
|200*x/255
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|-
|2C
|
|AirVol
|Air Volume
|
|x
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|-
|3C
|
|O2Sensor2
|Oxygen Sensor #2
|V
|0.01952*x
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|-
|55
|
|DecelLeanTPS
|Deceleration Leaning (decreasing TPS)
|%
|x*100/255
|-
|6A
|
|knock_adc
|knock_adc_processed
|count
|x
|-
|6B
|
|knock_base
|knock_base
|count
|x
|-
|6C
|
|knock_var
|knock_var
|count
|x
|-
|6D
|
|knock_change
|knock_change
|count
|x
|-
|6E
|
|knock_dynamics
|knock_dynamics
|count
|x
|-
|6F
|
|knock_flag
|knock_flag
|count
|x
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|-
|8A
|
|LoadError
|Load Error
|load
|0.15625*x-20
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|}</text>
    <sha1>e1adbdef94c930ad03ee9ec0882266fdf18b7ee9</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>Development Tips</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>682</id>
    <parentid>680</parentid>
    <timestamp>2009-07-08T19:47:23Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>More language corrections about processors and platforms.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3807" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

If you only read one document about the Evo ECU hardware platform, read this one:

http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

That is the original [http://www.renesas.com/ Renesas] hardware manual for the SH-2 platform.

For looking up additional information, both the Evo VIII and IX processors are based on SH-2, with the IX processor being a SH-2E variant; specifically, VIIIs use the SH7052F platform, and IXs use SH7055F. The primary difference is that the Evo VIII ECU (SH7052F) has a 256KB ROM image and 12KB of RAM, while the IX ECU (SH7055F) has a 512KB ROM image and 32KB of RAM; otherwise, the hardware is essentially the same.

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.</text>
    <sha1>7893bb3c459edecf75ec5412c47f4d2ebd4fc6db</sha1>
  </revision>
  <revision>
    <id>678</id>
    <parentid>677</parentid>
    <timestamp>2009-09-21T19:36:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added a couple of  hardware manual links, minor reorg.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3905" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://svn.logic.net/trac/esm/browser/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://svn.logic.net/trac/esm/browser/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

For looking up additional information about the platform used in the Evo ECUs, both the Evo VIII and IX processors are based on SH-2, with the IX processor being a SH-2E variant; specifically, VIIIs use the SH7052F platform, and IXs use SH7055F. The primary difference is that the Evo VIII ECU (SH7052F) has a 256KB ROM image and 12KB of RAM, while the IX ECU (SH7055F) has a 512KB ROM image and 32KB of RAM; otherwise, the hardware is essentially the same.

; SH-2 Software Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

; SH7052F Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/e602185_sh7052f.pdf

; SH7055SF Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0045_sh7055s.pdf

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.</text>
    <sha1>c5449c4d7c043f64fcecac1f6d5fe43ce3e847e4</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>Immobilizer Disabling</title>
  <ns>0</ns>
  <id>150</id>
  <revision>
    <id>643</id>
    <parentid>642</parentid>
    <timestamp>2009-07-25T15:17:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Some quick updates.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2117" xml:space="preserve">Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:

* When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; the immobilizer code in 96530006 operates differently, and needs to be disabled when used on a USDM vehicle. (Update: this is no longer necessary for simply switching ROMs; see the first part of the [[96530006]] description for more details.)
* When the original immobilizer code has been lost due to user error, such as overwriting the original ROM on the vehicle with one found online without making a backup first.
* Your keyfob has been damaged, and the RFID tag can no longer be read properly by the ECU.


----
'''This information is provided solely to help you restore the operation of ''your own'' vehicle; this website's operators and authors do not endorse the use of this information for mischief or illegal purposes.'''
----


First, please read the page [[Periphery Configuration]]; you'll need to add the configuration information shown there to be able to do this. (This should no longer be necessary with newer versions of EcuFlash, although the periphery values are unlabeled.)

Once you've added that information, open EcuFlash and load your ROM. Scroll down to the "ECUPeriphery" section, and open the "ECU Periphery 0 (FAA) Bits" table. You should see a table of choices, one of which is "Immobilizer Enabled?", with a "1" in the column next to it. Select the field with "1" in it, and press the "[" key to change it to a "0" instead. You should see the entire bottom half of the column show an indication that it was changed; this is normal, because you're actually changing that whole byte of information, not just the bit you just edited.

After saving your work, simply upload your changes to the ECU as you normally would, and your immobilizer should now be disabled. To test, simply leave your car parked in a bad neighborhood overnight.

'''WARNING''': Be aware that this disables an important security feature of your vehicle, and should not be done without understanding the full impact of the change.</text>
    <sha1>924a598728ee4edcede7b222c5972428b37d8326</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>Downloads</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>385</id>
    <parentid>364</parentid>
    <timestamp>2009-09-17T14:38:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Add link to 95960000.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2102" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|Replacement for USDM 2005 8
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>1c265cc188bfc50755da43beb721ab5e04c734d2</sha1>
  </revision>
  <revision>
    <id>355</id>
    <timestamp>2009-10-17T15:06:02Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added new Mirage ROM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2149" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|USDM
|Mirage LS 1.8 
|[[90160003]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|Replacement for USDM 2005 8
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>ad71079f2f618355256a33f67ba2a2d2bfc467f9</sha1>
  </revision>
  <revision>
    <id>356</id>
    <parentid>355</parentid>
    <timestamp>2009-10-23T13:05:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add 98650015.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2189" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|USDM
|Mirage LS 1.8 
|[[90160003]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650015]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|Replacement for USDM 2005 8
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>76f9be066de573cb6de122039b5006685f6377f7</sha1>
  </revision>
  <revision>
    <id>357</id>
    <parentid>356</parentid>
    <timestamp>2009-10-23T14:42:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2223" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|USDM
|Mirage LS 1.8 
|[[90160003]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650015]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|Replacement for USDM 2005 8
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|
|Evo 9
|[[88580015]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>c33cc6311318aa9ce40292330ae04aa59a3a2b4e</sha1>
  </revision>
  <revision>
    <id>364</id>
    <parentid>357</parentid>
    <timestamp>2009-11-05T15:37:26Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2218" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|USDM
|Mirage LS 1.8 
|[[90160003]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650015]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|"Universal" VIII ROM.
|-
|2005
|USDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|
|Evo 9
|[[88580015]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>b288453be4b7f43a0c031a3039f69de0b944b4ec</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:95960000.zip</title>
  <ns>6</ns>
  <id>224</id>
  <revision>
    <id>828</id>
    <timestamp>2009-09-17T14:40:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>95960000 ROM</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">95960000 ROM</text>
    <sha1>c0d75e6537d5884e22d900c7920fd8817f13783b</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>95960000</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>831</id>
    <parentid>829</parentid>
    <timestamp>2009-09-17T14:44:18Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '==Information== Car:  Mitsubishi Lancer Evolution 8  Year: 2004  Market: USDM  Case id:  ==Replacements==  ==Download files== [[Image:95960000.zip]]  ==RAM Addresses==  ;MUT Tabl…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="435" xml:space="preserve">==Information==
Car:  Mitsubishi Lancer Evolution 8

Year: 2004

Market: USDM

Case id:

==Replacements==

==Download files==
[[Image:95960000.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;33390&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|95960000]]</text>
    <sha1>5beec2c449c1820bd53aaf2144c79dc3d14bd561</sha1>
  </revision>
  <revision>
    <id>830</id>
    <parentid>829</parentid>
    <timestamp>2009-09-17T14:48:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="493" xml:space="preserve">==Information==
Car:  Mitsubishi Lancer Evolution 8

Year: Unknown

Market: Australia

Case id:

==Discussion==
http://forums.openecu.org/viewtopic.php?f=55&amp;t=4323

==Download files==
[[Image:95960000.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;33390&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|95960000]]</text>
    <sha1>c89302e728d68286ea0785f106d34eaa34d0dad5</sha1>
  </revision>
  <revision>
    <id>829</id>
    <timestamp>2009-09-17T14:48:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="503" xml:space="preserve">==Information==
Car:  Mitsubishi Lancer Evolution 8 (6-speed)

Year: Unknown

Market: Australia

Case id:

==Discussion==
http://forums.openecu.org/viewtopic.php?f=55&amp;t=4323

==Download files==
[[Image:95960000.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;33390&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|95960000]]</text>
    <sha1>d843627fa2797f8ffeacb88d5816f976e9840178</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:96420008.zip</title>
  <ns>6</ns>
  <id>226</id>
  <revision>
    <id>832</id>
    <timestamp>2009-09-20T12:46:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>96420008 Stock ROM</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">96420008 Stock ROM</text>
    <sha1>c1964e0daf16af50f4ed2350c25c8239e44292aa</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>96420008</title>
  <ns>0</ns>
  <id>227</id>
  <revision>
    <id>833</id>
    <timestamp>2009-09-20T12:47:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Initial addition.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="454" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 8 RS

Year: 2004

Market: USDM

Case id: 

==Replacements==

==Download==
[[Image:96420008.zip]]

==Addresses==

;MUT Table
:&lt;tt&gt;38158&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;

[[Category:ROMs|96420008]]</text>
    <sha1>402f48cf14a139f969e518b4eeccc08de97f5aaf</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>96530006</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>213</id>
    <parentid>199</parentid>
    <timestamp>2009-09-21T13:03:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Small language change noting that we use this ROM for all VIII cars now.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4200" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM, and has been successfully used to replace many other Evo VIII ROMs as well.

==96940011 (and other) Replacement Notes==

The immobilizer functions differently between [[96940011]] (or your original ROM) and [[96530006]], and you will need to change the behavior for the car to start correctly. You can either [[Immobilizer Disabling|disable the immobilizer]] completely, or change the [[96530006]] immobilizer behavior to function like your original ROM did. ''Only do one, or the other;'' if you disable the immobilizer completely, there is no need to do the following, and if you do the following you should definitely leave the immobilizer enabled for your own security.

To change the behavior, you'll need to add the following to both &lt;tt&gt;96940011.xml&lt;/tt&gt; and &lt;tt&gt;96530006.xml&lt;/tt&gt;:

 &amp;lt;table name="Immobilizer Hex" category="Misc" address="ffa" type="1D" level="2" scaling="Hex16"/&amp;gt;

Then, open your original [[96940011]] ROM, and copy the value from the "Immobilizer Hex" table under the "Misc" section (probably 0x0058). Open your new [[96530006]] ROM, and open the "Immobilizer Hex" table. You'll see that the value is probably 0x004D; paste in the value you copied from your [[96940011]] ROM in its place.

Then, do the same thing for the "Immobilizer" table under the "Misc" section.

At this point, your car should start as expected, with the immobilizer functioning correctly.

For more information on this swap, please read the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM.

==Download==
[[Image:96530006.HEX]]

[[Image:Def_file_96530006_tephra510_new_tables_20081101.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

There are 4 different 2-byte Load choices each with different correction factors. 

;2-byte LOAD_Raw (no temp compensation)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;2-byte LOAD_Temp_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8986&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8987&lt;/tt&gt;

;2-byte LOAD_Baro_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8988&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8989&lt;/tt&gt;

;2-byte LOAD_Temp_and_Baro_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

Load correction note: The ECU uses the following logic to find the lookup info it needs:

Fuel maps will either use Load_Raw OR LOAD_Temp_and_Baro_Compensated depending on an certain conditions

Ignition Maps will either use LOAD_Baro_Compensated OR LOAD_Temp_and_Baro_Compensated depending on the MAF IAT. (Thanks to Tephra for this info). 

It is typically best to use the 2-byte LOAD_Temp_and_Baro_Compensated for tuning, while taking into account the lookup factors mentioned above for both Fuel and Ignition Timing. This will allow the tuner to accurately tune ignition timing while being able to compensate for the lookup logic for fueling. LOAD_Raw is typically 10-20 points higher than LOAD_Temp_and_Baro_Compensated at peak boost. You must take this into account when tuning using the 2-byte loads. With the advent of Tehpra's 1byte load(using a Tephra Mod ROM), you can use 1byte load(which is actually LOAD_Raw) to log LOAD_Raw. You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you. 


Other Addresses:

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>67ecaee74b02b80e77d337948617fb8d8f9bfed7</sha1>
  </revision>
  <revision>
    <id>214</id>
    <parentid>213</parentid>
    <timestamp>2009-09-21T13:05:10Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* 96940011 (and other) Replacement Notes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4249" xml:space="preserve">96530006 is a 2005 EDM [[Wikipedia:Mitsubishi Lancer Evolution|Evo]] ROM, commonly used to replace the [[96940011]] USDM ROM, and has been successfully used to replace many other Evo VIII ROMs as well.

==96940011 (and other) Replacement Notes==

The immobilizer functions differently between [[96940011]] (or your original ROM) and [[96530006]], and you will need to change the behavior for the car to start correctly. You can either [[Immobilizer Disabling|disable the immobilizer]] completely, or change the [[96530006]] immobilizer behavior to function like your original ROM did. ''Only do one, or the other;'' if you disable the immobilizer completely, there is no need to do the following, and if you do the following you should definitely leave the immobilizer enabled for your own security.

To change the behavior, you'll need to add the following to both &lt;tt&gt;96940011.xml&lt;/tt&gt; and &lt;tt&gt;96530006.xml&lt;/tt&gt; (or the base XML for the ROM you're coming from):

 &amp;lt;table name="Immobilizer Hex" category="Misc" address="ffa" type="1D" level="2" scaling="Hex16"/&amp;gt;

Then, open your original [[96940011]] ROM, and copy the value from the "Immobilizer Hex" table under the "Misc" section (probably 0x0058). Open your new [[96530006]] ROM, and open the "Immobilizer Hex" table. You'll see that the value is probably 0x004D; paste in the value you copied from your [[96940011]] ROM in its place.

Then, do the same thing for the "Immobilizer" table under the "Misc" section.

At this point, your car should start as expected, with the immobilizer functioning correctly.

For more information on this swap, please read the [http://forums.evolutionm.net/showthread.php?t=326487 original] [http://forums.evolutionm.net/showthread.php?t=334065 threads] on EvoM.

==Download==
[[Image:96530006.HEX]]

[[Image:Def_file_96530006_tephra510_new_tables_20081101.zip]]

==EcuFlash Definition Errors==

Injector Battery Voltage Latency Compensation is incorrect in the original EcuFlash &lt;tt&gt;96539996.xml&lt;/tt&gt; file. Replace it with:

 &amp;lt;table name="Injector Battery Voltage Latency Compensation" address="37c0"&amp;gt;
     &amp;lt;table name="Battery Voltage" address="67f0" elements="7"/&amp;gt;
 &amp;lt;/table&amp;gt;

Note: '''The zipped xml on this page has this corrected already.''' The error is located in the standard xml which comes with Ecuflash intallation.

==Addresses==

;MUT Table
:&lt;tt&gt;36200&lt;/tt&gt;

There are 4 different 2-byte Load choices each with different correction factors. 

;2-byte LOAD_Raw (no temp compensation)
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8984&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8985&lt;/tt&gt;

;2-byte LOAD_Temp_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8986&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8987&lt;/tt&gt;

;2-byte LOAD_Baro_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;8988&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;8989&lt;/tt&gt;

;2-byte LOAD_Temp_and_Baro_Compensated
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;898A&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;898B&lt;/tt&gt;

Load correction note: The ECU uses the following logic to find the lookup info it needs:

Fuel maps will either use Load_Raw OR LOAD_Temp_and_Baro_Compensated depending on an certain conditions

Ignition Maps will either use LOAD_Baro_Compensated OR LOAD_Temp_and_Baro_Compensated depending on the MAF IAT. (Thanks to Tephra for this info). 

It is typically best to use the 2-byte LOAD_Temp_and_Baro_Compensated for tuning, while taking into account the lookup factors mentioned above for both Fuel and Ignition Timing. This will allow the tuner to accurately tune ignition timing while being able to compensate for the lookup logic for fueling. LOAD_Raw is typically 10-20 points higher than LOAD_Temp_and_Baro_Compensated at peak boost. You must take this into account when tuning using the 2-byte loads. With the advent of Tehpra's 1byte load(using a Tephra Mod ROM), you can use 1byte load(which is actually LOAD_Raw) to log LOAD_Raw. You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you. 


Other Addresses:

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;8962&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;8963&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;89E2&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;89E3&lt;/tt&gt;
[[Category:ROMs|96530006]]</text>
    <sha1>3fa71525c89541151d49890338559dc38c99656e</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:88590015.zip</title>
  <ns>6</ns>
  <id>228</id>
  <revision>
    <id>834</id>
    <timestamp>2009-09-27T18:50:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Stock 88590015 ROM, from http://www.osecuroms.org/.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="51" xml:space="preserve">Stock 88590015 ROM, from http://www.osecuroms.org/.</text>
    <sha1>0a5eaa7103ca05f755835d34531d872c486fcab1</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>88590015</title>
  <ns>0</ns>
  <id>136</id>
  <revision>
    <id>575</id>
    <parentid>574</parentid>
    <timestamp>2009-09-27T18:50:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add link to stock 88590015 image.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1800" xml:space="preserve">88590015 is considered the final updated / current ROM for 2006 USDM [[Wikipedia:Mitsubishi Lancer Evolution| Evo IX]]

Stock version of ROM: [[Image:88590015.zip]]

'''Please read the !Readme.txt''' included in zip files

* Tephra v5.10, MrFred Defs [[image:88590015-v5.10.zip]]

* Tephra v5.10, MrFred Defs, JDM MAP [[image:88590015-v5.10-JDM_MAP.zip]]

* Tephra v5.10, MrFred Defs, JDM MAP, Direct Boost Control [[image:88590015-v5.10-Direct_Boost_Ctl.zip]]

This is the rom commonly included with all USDM Evo IX.

==RAM Addresses==
Please note that the displayed MUT locations are only a recommendation.

;MUT Table
:&lt;tt&gt;3EE84&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6B42&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;6B43&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6B1E&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6B1F&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B9E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B9F&lt;/tt&gt;

;[http://forums.evolutionm.net/ecuflash/290867-nolift-shift-6.html#post4793090 Clutch Switch]
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6A35&lt;/tt&gt;
*Must log x bit 1 to get only clutch request.
&lt;nowiki&gt;&lt;DataListItem DataLog="Y" Display="ClutchFlag" LogReference="ClutchFlag" RequestID="00" Eval="x bit 1" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="1" ChartMin="0" ChartMax="1" Notes=""/&gt;&lt;/nowiki&gt;
;Acceleration
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6A35&lt;/tt&gt; (same as clutch)
*Must log x bit 16 to get only accelleration request.
&lt;nowiki&gt;&lt;DataListItem DataLog="Y" Display="ClutchFlag" LogReference="ClutchFlag" RequestID="00" Eval="x bit 16" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="1" ChartMin="0" ChartMax="1" Notes=""/&gt;&lt;/nowiki&gt;

&lt;br&gt;
&lt;br&gt;
To disable Cold Start Ignition Tables - Periphery0 (FAA) bit9 must be set to 0 (i.e, 0x56DA -&gt; 0x54DA will disable)

[[Category:ROMs|88590015]]</text>
    <sha1>c9f096e1191034c861cca70e5922837953aedf9b</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>MUT Commands</title>
  <ns>0</ns>
  <id>229</id>
  <revision>
    <id>836</id>
    <parentid>835</parentid>
    <timestamp>2009-10-06T00:11:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], w…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1355" xml:space="preserve">MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], which correspond to locations in the MUT table.

&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!Description
|-
|C0
|
|-
|C1
|
|-
|C2
|
|-
|C3
|SAS (Secondary Air System) - for BISS screw adjustments
|-
|C4
|
|-
|C5
|
|-
|C6
|
|-
|C7
|
|-
|C8
|
|-
|C9
|
|-
|CA
|Invalid command
|-
|CB
|Invalid command
|-
|CC
|
|-
|CD
|A/C fan high
|-
|CE
|A/C fan low
|-
|CF
|Main fan high
|-
|D0
|Main fan low
|-
|D1
|
|-
|D2
|
|-
|D3
|
|-
|D4
|
|-
|D5
|EGR solenoid
|-
|D6
|
|-
|D7
|Purge solenoid
|-
|D8
|Fuel pump
|-
|D9
|Fix timing at 5 degrees
|-
|DA
|Disable injector 1
|-
|DB
|Disable injector 2
|-
|DC
|Disable injector 3
|-
|DD
|Disable injector 4
|-
|DE
|Disable injector 5 (unused)
|-
|DF
|Disable injector 6 (unused)
|-
|E0
|
|-
|E1
|
|-
|E2
|
|-
|E3
|
|-
|E4
|
|-
|E5
|
|-
|E6
|
|-
|E7
|
|-
|E8
|
|-
|E9
|
|-
|EA
|
|-
|EB
|
|-
|EC
|Calibration F6A
|-
|ED
|Calibration
|-
|EE
|Calibration
|-
|EF
|Calibration
|-
|F0
|
|-
|F1
|
|-
|F2
|
|-
|F3
|
|-
|F4
|
|-
|F5
|
|-
|F6
|
|-
|F7
|
|-
|F8
|
|-
|F9
|
|-
|FA
|Clear active and stored faults
|-
|FB
|Force tests to run
|-
|FC
|Clear active faults
|-
|FD
|
|-
|FE
|Immobilizer
|-
|FF
|Init code
|}
&lt;/center&gt;</text>
    <sha1>40435d020cb9763bb5b4de341482143aa704dbbc</sha1>
  </revision>
  <revision>
    <id>837</id>
    <parentid>835</parentid>
    <timestamp>2009-10-06T13:05:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1462" xml:space="preserve">MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], which correspond to locations in the MUT table.

&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!Description
|-
|C0
|
|-
|C1
|
|-
|C2
|
|-
|C3
|SAS ([[Speed Adjusting Screw]]) - for adjusting the amount of air allowed to bypass the throttle body when the ISC is not in use and the throttle plate is closde.
|-
|C4
|
|-
|C5
|
|-
|C6
|
|-
|C7
|
|-
|C8
|
|-
|C9
|
|-
|CA
|Invalid command
|-
|CB
|Invalid command
|-
|CC
|
|-
|CD
|A/C fan high
|-
|CE
|A/C fan low
|-
|CF
|Main fan high
|-
|D0
|Main fan low
|-
|D1
|
|-
|D2
|
|-
|D3
|
|-
|D4
|
|-
|D5
|EGR solenoid
|-
|D6
|
|-
|D7
|Purge solenoid
|-
|D8
|Fuel pump
|-
|D9
|Fix timing at 5 degrees
|-
|DA
|Disable injector 1
|-
|DB
|Disable injector 2
|-
|DC
|Disable injector 3
|-
|DD
|Disable injector 4
|-
|DE
|Disable injector 5 (unused)
|-
|DF
|Disable injector 6 (unused)
|-
|E0
|
|-
|E1
|
|-
|E2
|
|-
|E3
|
|-
|E4
|
|-
|E5
|
|-
|E6
|
|-
|E7
|
|-
|E8
|
|-
|E9
|
|-
|EA
|
|-
|EB
|
|-
|EC
|Calibration F6A
|-
|ED
|Calibration
|-
|EE
|Calibration
|-
|EF
|Calibration
|-
|F0
|
|-
|F1
|
|-
|F2
|
|-
|F3
|
|-
|F4
|
|-
|F5
|
|-
|F6
|
|-
|F7
|
|-
|F8
|
|-
|F9
|
|-
|FA
|Clear active and stored faults
|-
|FB
|Force tests to run
|-
|FC
|Clear active faults
|-
|FD
|
|-
|FE
|Immobilizer
|-
|FF
|Init code
|}
&lt;/center&gt;</text>
    <sha1>a817b16517344e805f4bf454956cecb211ee7d41</sha1>
  </revision>
  <revision>
    <id>835</id>
    <timestamp>2009-11-08T14:30:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added D3 and D6 per Deepnine.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1503" xml:space="preserve">MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], which correspond to locations in the MUT table.

&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!Description
|-
|C0
|
|-
|C1
|
|-
|C2
|
|-
|C3
|SAS ([[Speed Adjusting Screw]])
for adjusting the amount of air allowed to bypass the throttle body when the ISC is not in use and the throttle plate is closed
|-
|C4
|
|-
|C5
|
|-
|C6
|
|-
|C7
|
|-
|C8
|
|-
|C9
|
|-
|CA
|Invalid command
|-
|CB
|Invalid command
|-
|CC
|
|-
|CD
|A/C fan high
|-
|CE
|A/C fan low
|-
|CF
|Main fan high
|-
|D0
|Main fan low
|-
|D1
|
|-
|D2
|
|-
|D3
|Boost control solenoid
|-
|D4
|
|-
|D5
|EGR solenoid
|-
|D6
|Fuel pressure solenoid
|-
|D7
|Purge solenoid
|-
|D8
|Fuel pump
|-
|D9
|Fix timing at 5 degrees
|-
|DA
|Disable injector 1
|-
|DB
|Disable injector 2
|-
|DC
|Disable injector 3
|-
|DD
|Disable injector 4
|-
|DE
|Disable injector 5 (unused)
|-
|DF
|Disable injector 6 (unused)
|-
|E0
|
|-
|E1
|
|-
|E2
|
|-
|E3
|
|-
|E4
|
|-
|E5
|
|-
|E6
|
|-
|E7
|
|-
|E8
|
|-
|E9
|
|-
|EA
|
|-
|EB
|
|-
|EC
|Calibration F6A
|-
|ED
|Calibration
|-
|EE
|Calibration
|-
|EF
|Calibration
|-
|F0
|
|-
|F1
|
|-
|F2
|
|-
|F3
|
|-
|F4
|
|-
|F5
|
|-
|F6
|
|-
|F7
|
|-
|F8
|
|-
|F9
|
|-
|FA
|Clear active and stored faults
|-
|FB
|Force tests to run
|-
|FC
|Clear active faults
|-
|FD
|
|-
|FE
|Immobilizer
|-
|FF
|Init code
|}
&lt;/center&gt;</text>
    <sha1>89168eb194a2207f91578e93f414596df89969ba</sha1>
  </revision>
  <revision>
    <id>838</id>
    <parentid>835</parentid>
    <timestamp>2009-11-08T14:32:18Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added F9 per Deepnine.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1574" xml:space="preserve">MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], which correspond to locations in the MUT table.

&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!Description
|-
|C0
|
|-
|C1
|
|-
|C2
|
|-
|C3
|SAS ([[Speed Adjusting Screw]])
for adjusting the amount of air allowed to bypass the throttle body when the ISC is not in use and the throttle plate is closed
|-
|C4
|
|-
|C5
|
|-
|C6
|
|-
|C7
|
|-
|C8
|
|-
|C9
|
|-
|CA
|Invalid command
|-
|CB
|Invalid command
|-
|CC
|
|-
|CD
|A/C fan high
|-
|CE
|A/C fan low
|-
|CF
|Main fan high
|-
|D0
|Main fan low
|-
|D1
|
|-
|D2
|
|-
|D3
|Boost control solenoid
|-
|D4
|
|-
|D5
|EGR solenoid
|-
|D6
|Fuel pressure solenoid
|-
|D7
|Purge solenoid
|-
|D8
|Fuel pump
|-
|D9
|Fix timing at 5 degrees
|-
|DA
|Disable injector 1
|-
|DB
|Disable injector 2
|-
|DC
|Disable injector 3
|-
|DD
|Disable injector 4
|-
|DE
|Disable injector 5 (unused)
|-
|DF
|Disable injector 6 (unused)
|-
|E0
|
|-
|E1
|
|-
|E2
|
|-
|E3
|
|-
|E4
|
|-
|E5
|
|-
|E6
|
|-
|E7
|
|-
|E8
|
|-
|E9
|
|-
|EA
|
|-
|EB
|
|-
|EC
|Calibration F6A
|-
|ED
|Calibration
|-
|EE
|Calibration
|-
|EF
|Calibration
|-
|F0
|
|-
|F1
|
|-
|F2
|
|-
|F3
|
|-
|F4
|
|-
|F5
|
|-
|F6
|
|-
|F7
|
|-
|F8
|
|-
|F9
|some keep alive function to keep the accuator engaged. response is 0xff
|-
|FA
|Clear active and stored faults
|-
|FB
|Force tests to run
|-
|FC
|Clear active faults
|-
|FD
|
|-
|FE
|Immobilizer
|-
|FF
|Init code
|}
&lt;/center&gt;</text>
    <sha1>6e4a8d7debf349dacf5b6b2ac71f0c2b06ad2441</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>MUT Requests</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>815</id>
    <parentid>808</parentid>
    <timestamp>2009-10-06T00:11:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6848" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|}
&lt;/center&gt;</text>
    <sha1>38d7e3e8b0c1ad78a2f5008033f2e44265074719</sha1>
  </revision>
  <revision>
    <id>819</id>
    <parentid>808</parentid>
    <timestamp>2009-10-10T15:26:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>A few updates from acamus.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7759" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|}
&lt;/center&gt;</text>
    <sha1>044eb54a2f7a1813f161a8ddd7cae8c9ee940ef4</sha1>
  </revision>
  <revision>
    <id>820</id>
    <parentid>808</parentid>
    <timestamp>2009-10-10T15:27:28Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Fix table formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7759" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|}
&lt;/center&gt;</text>
    <sha1>a80b486f98ed778b95293cd63f299de0d412f9dd</sha1>
  </revision>
  <revision>
    <id>817</id>
    <parentid>808</parentid>
    <timestamp>2009-11-19T16:44:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add more acamus findings.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8045" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|52
|
|
|Rear Long Fuel Trim Bank 1
|
|
|
|-
|53
|
|
|Rear Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|60
|
|
|Rear O2 Trim - Low
|
|
|
|-
|61
|
|
|Rear O2 Trim - Mid
|
|
|
|-
|62
|
|
|Rear O2 Trim - High
|
|
|
|-
|63
|
|
|Rear O2 Feedback Trim
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|96
|
|MAF_ADC
|RAW MAF ADC value 
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|}
&lt;/center&gt;</text>
    <sha1>8112ba8adab7ecd6baa846391953c0838454f145</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>Speed Adjusting Screw</title>
  <ns>0</ns>
  <id>230</id>
  <revision>
    <id>842</id>
    <timestamp>2009-10-06T13:05:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'The following procedure is from the factory service manual. For our purposes, replace the use of the factory scantool MB991958 with a datalogger with actuator control, such as [[…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2046" xml:space="preserve">The following procedure is from the factory service manual. For our purposes, replace the use of the factory scantool MB991958 with a datalogger with actuator control, such as [[EvoScan]], or one which allows arbitrary commands to be sent (see the [[MUT Commands]] page for the command ID to send for SAS control).

== Adjustment Procedure ==

'''''NOTE:'' The standard idle speed has been adjusted with the speed adjusting screw (SAS), by the manufacturer, and there should be no need for readjustment.'''

''NOTE:'' If the adjustment has been changed by mistake, the idle speed may become too high or the idle speed may drop too low when loads A/C, defogger, etc. are placed on the engine. If this occurs, adjust by the following procedure.

''NOTE:'' The adjustment, if made, should be made after first confirming that the spark plugs, the injectors, the idle air control motor, compression, etc., are all normal.

# The vehicle should be prepared as follows before the inspection and adjustment.
#* Engine coolant temperature: 80 − 95°C (176 − 203°F)
#* Lights, electric cooling fan and accessories: OFF
#* Transaxle: Neutral
# Connect scan tool MB991958 to the data link connector (16-pin). '''''CAUTION:'' To prevent damage to scan tool MB991958, always turn the ignition switch to the "LOCK" (OFF) position before connecting or disconnecting scan tool MB991958.'''
# Start the engine and run at idle.
# Select the item number 30 of the scan tool Actuator test. NOTE: Use the scan tool to hold the IAC motor at the basic step to adjust the basic idle speed.
# Check the idle speed. ''Standard value:'' 850 ± 50 r/min

''NOTE:'' The engine speed may be 20 to 100 r/min lower than indicated above for a new vehicle [driven approximately 500 km (300 mile) or less], but no adjustment is necessary.

''NOTE:'' If the engine stalls or the engine speed is low even though the vehicle has been driven approximately 500 km (300 mile) or more, it is probable that deposits are adhered to the throttle valve, so clean it. (Refer to P.13A-813.)</text>
    <sha1>2bfc68ec4a999eae652e65c0b35345934cc7265e</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:90160003.hex</title>
  <ns>6</ns>
  <id>231</id>
  <revision>
    <id>843</id>
    <timestamp>2009-10-17T15:08:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>90160003 ROM from a 2002 Mitsubishi Mirage LS 1.8 4g93.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55" xml:space="preserve">90160003 ROM from a 2002 Mitsubishi Mirage LS 1.8 4g93.</text>
    <sha1>acf2590386124bfc206f5dd12fe445fac76a88dd</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>93390000</title>
  <ns>0</ns>
  <id>153</id>
  <revision>
    <id>672</id>
    <parentid>671</parentid>
    <timestamp>2009-10-17T15:12:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="536" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 7

Year: 2001

Market: japanese (JDM)

Case id: 

==Replacements==

This rom can be replaced with [[90550001]] ( has no rear O2, no immobilizer)

==Download files==
[[Image:93390000_EVO7_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;302dc&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|93390000]]</text>
    <sha1>c889f61a829dcb996211123476f82b02ce2bbb3c</sha1>
  </revision>
  <revision>
    <id>671</id>
    <parentid>669</parentid>
    <timestamp>2009-10-18T03:11:30Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/EdwardMarshall|EdwardMarshall]] ([[User talk:EdwardMarshall|Talk]]) to last revision by [[User:Deepnine|Deepnine]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="536" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 7

Year: 2001

Market: japanese (JDM)

Case id: 

==Replacements==

This rom can be replaced with [[90550001]] ( has no rear O2, no immobilizer)

==Download files==
[[Image:93390000_EVO7_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;302d8&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|93390000]]</text>
    <sha1>5f618e1e2868d07b92d3d6b33e103de7ac02ffc1</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>90160003</title>
  <ns>0</ns>
  <id>232</id>
  <revision>
    <id>845</id>
    <parentid>844</parentid>
    <timestamp>2009-10-17T15:26:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '==Information== Car:  Mitsubisshi Mirage LS 1.8 4g93  Year: 2002  Market: United States (USDM))  Case id:   ==Discussion==  http://forums.evolutionm.net/ecuflash/453183-i-need-de…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="542" xml:space="preserve">==Information==
Car:  Mitsubisshi Mirage LS 1.8 4g93

Year: 2002

Market: United States (USDM))

Case id: 

==Discussion==

http://forums.evolutionm.net/ecuflash/453183-i-need-definitions-rom-90160003-please.html

==Download files==
[[Image:90160003.hex]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;302d8&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|90160003]]</text>
    <sha1>75a7c4913747a8af3757f1de8bb9ec55530a7965</sha1>
  </revision>
  <revision>
    <id>844</id>
    <timestamp>2009-10-18T03:11:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Fix MUT address</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="542" xml:space="preserve">==Information==
Car:  Mitsubisshi Mirage LS 1.8 4g93

Year: 2002

Market: United States (USDM))

Case id: 

==Discussion==

http://forums.evolutionm.net/ecuflash/453183-i-need-definitions-rom-90160003-please.html

==Download files==
[[Image:90160003.hex]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;302dc&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|90160003]]</text>
    <sha1>dd29781afa4de19b036686cb5ef409b9e01ed977</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:98650015.zip</title>
  <ns>6</ns>
  <id>233</id>
  <revision>
    <id>846</id>
    <timestamp>2009-10-23T13:06:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>98650015 ROM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">98650015 ROM.</text>
    <sha1>eaadf0a6a6abadc50b6aa15fda1277488fb92654</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>98650015</title>
  <ns>0</ns>
  <id>234</id>
  <revision>
    <id>847</id>
    <timestamp>2009-10-23T13:07:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '==Information== Car:  Mitsubisshi Lancer Evolution 7  Year: 2003  Market: EDM  Case id:  ==Download files== [[Image:98650015.zip]]  ==RAM Addresses==  ;MUT Table :&lt;tt&gt;&lt;/tt&gt;  ;2-b…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="412" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 7

Year: 2003

Market: EDM

Case id:

==Download files==
[[Image:98650015.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|98650015]]</text>
    <sha1>805171eb41276b6fbb358ef247b31ce2bee6b991</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:88580015.zip</title>
  <ns>6</ns>
  <id>235</id>
  <revision>
    <id>848</id>
    <timestamp>2009-10-23T14:30:02Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>88580015 ROM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">88580015 ROM.</text>
    <sha1>3af7dea52670c7dbc6a0081a7856061f6ffd26fe</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>88580015</title>
  <ns>0</ns>
  <id>236</id>
  <revision>
    <id>849</id>
    <timestamp>2009-10-23T14:42:26Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '==Information== Car:  Mitsubisshi Lancer Evolution 9  Year:  Market:  Case id:   ==Replacements==  ==Download files== [[Image:88580015.zip]]  ==RAM Addresses==  ;MUT Table :&lt;tt&gt;3…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="451" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year:

Market:

Case id: 

==Replacements==

==Download files==
[[Image:88580015.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;374dc&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6B22&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;6B23&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6AFE&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6AFF&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B7E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B7F&lt;/tt&gt;

[[Category:ROMs|88580015]]</text>
    <sha1>96cd3896606ff8b4f9df62209a0e597a374c13fd</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>88580013</title>
  <ns>0</ns>
  <id>210</id>
  <revision>
    <id>789</id>
    <timestamp>2009-10-23T14:42:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add 2-byte values and MUT location.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="462" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year:

Market:

Case id: 

==Replacements==

==Download files==
[[Image:88580013_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;373c4&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6B22&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;6B23&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6AFE&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6AFF&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B7E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B7F&lt;/tt&gt;

[[Category:ROMs|88580013]]</text>
    <sha1>eb5c71b0147f4524d93504d88b391240ffcbbbbd</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>OBD Pinout</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>854</id>
    <parentid>850</parentid>
    <timestamp>2009-11-08T14:12:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]): {| | 1||Diagnosis control line  |- | 2||J1850 (+) line |- | 3||Suspension - ECS -  |…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="684" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):
{|
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Gnd
|-
| 5||Gnd
|-
| 6||Transmission - ELC-4/5AT 
|-
| 7||К-Line (ISO 9141) 
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|-
|21||Traction – TCL/4WD 
|-
|22||Steering - 4WS/ECPS 
|-
|25||ECU
|-
|26||ECU programing
|-
|27||Transmission ECU programming
|-
|32||Adapter identification
|}</text>
    <sha1>b12fc9f2400da9db4f613afe4e0a756c9520dcd5</sha1>
  </revision>
  <revision>
    <id>852</id>
    <parentid>850</parentid>
    <timestamp>2009-11-29T18:27:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Make separation between 16/21 and 27/32 more obvious.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="737" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):
{| border=1 cellspacing=0
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Gnd
|-
| 5||Gnd
|-
| 6||Transmission - ELC-4/5AT 
|-
| 7||К-Line (ISO 9141) 
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|-
|colspan=2|
|-
|21||Traction – TCL/4WD 
|-
|22||Steering - 4WS/ECPS 
|-
|25||ECU
|-
|26||ECU programing
|-
|27||Transmission ECU programming
|-
|colspan=2|
|-
|32||Adapter identification
|}</text>
    <sha1>bddf107db1798e9cc691030ea36189ce935b0f48</sha1>
  </revision>
  <revision>
    <id>856</id>
    <parentid>850</parentid>
    <timestamp>2009-11-29T18:31:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="774" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Gnd
|-
| 5||Gnd
|-
| 6||Transmission - ELC-4/5AT 
|-
| 7||К-Line (ISO 9141) 
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|-
|colspan=2|
|-
|21||Traction – TCL/4WD 
|-
|22||Steering - 4WS/ECPS 
|-
|25||ECU
|-
|26||ECU programing
|-
|27||Transmission ECU programming
|-
|colspan=2|
|-
|32||Adapter identification
|}</text>
    <sha1>8e8c60ef4ce6466b710c8fcc52b192d810f8ad71</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>ECU Development</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>655</id>
    <parentid>647</parentid>
    <timestamp>2009-11-08T14:34:02Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Reworked to include links of interest to developers.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="376" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Communications ==

* [[OBD_Pinout]]
* [[MUT_Requests]]
* [[MUT_Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>9afd7f1b33d4a0259b1943b07fa7e5b918db1d91</sha1>
  </revision>
  <revision>
    <id>651</id>
    <parentid>647</parentid>
    <timestamp>2009-11-28T08:35:30Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="410" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[ECU Wiring]]
* [[OBD_Pinout]]

== Communications ==

* [[MUT_Requests]]
* [[MUT_Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>8030b00b7f17d2b07ebc00611d5f2b18a468edb2</sha1>
  </revision>
  <revision>
    <id>650</id>
    <parentid>647</parentid>
    <timestamp>2009-11-28T08:35:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="410" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[ECU Wiring]]
* [[OBD Pinout]]

== Communications ==

* [[MUT_Requests]]
* [[MUT_Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>04aa1726955de99aab1eb1bc9aa2a8c305c6aade</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>MediaWiki:Developers</title>
  <ns>8</ns>
  <id>160</id>
  <revision>
    <id>686</id>
    <parentid>685</parentid>
    <timestamp>2009-11-08T14:38:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">'''For developers'''</text>
    <sha1>8a0930e8df09b6fa530d3a7c247607aa8df4bc2a</sha1>
  </revision>
  <revision>
    <id>687</id>
    <parentid>685</parentid>
    <timestamp>2009-11-08T14:39:04Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21" xml:space="preserve">&lt;b&gt;For developers&lt;/b&gt;</text>
    <sha1>bfb5b771f410ea03a372636192f903ab01c112a2</sha1>
  </revision>
  <revision>
    <id>685</id>
    <timestamp>2009-11-08T14:41:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14" xml:space="preserve">For developers</text>
    <sha1>f18d0d18586127e1f56da0a611a7144770659f55</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>34</id>
    <parentid>1</parentid>
    <timestamp>2009-11-08T14:45:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Development */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2469" xml:space="preserve">'''I ask that anyone who is going to edit or add to the wiki please browse through it thoroughly before adding content.  I have noticed that as the wiki is expanding we seem to be duplicating content.  For example we already have a page on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]],[[Glossary]] etc..  If you want to discuss these items please simply link to their wiki page and possibly add content there if needed.  We don't need to have several pages all talking about EvoScan for example.  THANKS FOR YOUR HELP'''


The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

==Warning==
Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Glossary==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU development (communications, disassembly, patching, etc), please see our [[ECU Development]] page.</text>
    <sha1>e1dfe50e82d82569dca7868eb9c6f784bff0a2fb</sha1>
  </revision>
  <revision>
    <id>33</id>
    <parentid>1</parentid>
    <timestamp>2009-11-08T14:45:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Development */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2456" xml:space="preserve">'''I ask that anyone who is going to edit or add to the wiki please browse through it thoroughly before adding content.  I have noticed that as the wiki is expanding we seem to be duplicating content.  For example we already have a page on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]],[[Glossary]] etc..  If you want to discuss these items please simply link to their wiki page and possibly add content there if needed.  We don't need to have several pages all talking about EvoScan for example.  THANKS FOR YOUR HELP'''


The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

==Warning==
Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.

==Glossary==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>a4df274b2d39dedb60eddd4bdda096ad2c782625</sha1>
  </revision>
</page>
<page arvcontinue="20090708194723|682">
  <title>File:OBD-connector-pinout.png</title>
  <ns>6</ns>
  <id>238</id>
  <revision>
    <id>862</id>
    <parentid>860</parentid>
    <timestamp>2009-11-29T18:31:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>OBD-II connector pinout</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">OBD-II connector pinout</text>
    <sha1>e1c54fd459b3cf181e8e8f11a47a1d906106b029</sha1>
  </revision>
  <revision>
    <id>858</id>
    <timestamp>2009-11-29T18:33:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">OBD-II connector pinout, taken from [http://en.wikipedia.org/wiki/File:OBD-connector-pinout.png Wikipedia] (released into the public domain).</text>
    <sha1>332e31623652eaf861e9f6b6db0d525dd20d041e</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>USDM VIII ECU Pinout</title>
  <ns>0</ns>
  <id>239</id>
  <revision>
    <id>864</id>
    <parentid>863</parentid>
    <timestamp>2009-11-29T18:36:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '== Evo VIII ==  The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and …'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4167" xml:space="preserve">== Evo VIII ==

The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

=== C-121 ===

{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


=== C-119 ===

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


=== C-117 ===

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


=== C-115 ===

{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>c6077a2ad657d68adf3912c4beb2ba8acc0db324</sha1>
  </revision>
  <revision>
    <id>865</id>
    <parentid>863</parentid>
    <timestamp>2009-11-29T18:40:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4135" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>3ea7a60f2ae18ddd64168580b9a5197cbe944f15</sha1>
  </revision>
  <revision>
    <id>869</id>
    <parentid>866</parentid>
    <timestamp>2009-11-29T18:47:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4741" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

{| border=0 cellspacing=0 cellpadding=5
|
{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}
|}


= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>51ed1a187820ac494bb7a35e3751d285db6e32be</sha1>
  </revision>
  <revision>
    <id>870</id>
    <parentid>866</parentid>
    <timestamp>2009-11-29T18:48:57Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4772" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}
|}


= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>d3b3dc44df796f8f0a169c746e69131d47dbc341</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>USDM IX ECU Pinout</title>
  <ns>0</ns>
  <id>240</id>
  <revision>
    <id>872</id>
    <timestamp>2009-11-29T18:36:31Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '== Evo IX ==  The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117. …'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4671" xml:space="preserve">== Evo IX ==

The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

=== C-121 ===

{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


=== C-119 ===

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


=== C-117 ===

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>9472249cd7014e880c6e344469841ff1e1c457f5</sha1>
  </revision>
  <revision>
    <id>874</id>
    <parentid>873</parentid>
    <timestamp>2009-11-29T18:39:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4645" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>bf380ab0b177f213eb091d2f7f6c700a91a886e8</sha1>
  </revision>
  <revision>
    <id>876</id>
    <parentid>873</parentid>
    <timestamp>2009-11-29T18:45:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5941" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= Complete harness =

{| border=0 cellspacing=0 cellpadding=5
|
{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}
|}


= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>ffb8381bf716aa3f9a0196c78a2685ddc9677326</sha1>
  </revision>
  <revision>
    <id>875</id>
    <parentid>873</parentid>
    <timestamp>2009-11-29T18:49:16Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5965" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= Complete harness =

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}
|}


= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|9||10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|24||25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||46||47
|-
|48||49||50||51||52||53||54||55||56||57||58||59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||67||68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||76||77
|-
|78||79||80||81||82||83||84||85||86||87||88||89||90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||99||100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>fb1fc1769dfeac1f5063fca5fade51c268a924d5</sha1>
  </revision>
  <revision>
    <id>877</id>
    <parentid>873</parentid>
    <timestamp>2010-01-05T20:48:28Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add information about large and small pins.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7457" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= Complete harness =

Pins 1, 2, 9, 10, 24, 25, 46, 47, 58, 59, 67, 68, 76, 77, 89, 90, 99, and 100 are the "large" variety (so, 6 per plug, or 18 total pins are large), and the remainder (29, 22, and 24 pins for each plug, or 75 total) are the "small" type. The large pins have been colored in yellow in the diagrams below.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}
|}


= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>4d255cb7bf7ec710ba62c7ae42e395826cb01352</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>Useful Tools</title>
  <ns>0</ns>
  <id>241</id>
  <revision>
    <id>880</id>
    <parentid>879</parentid>
    <timestamp>2009-11-29T18:37:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '= Useful Tools =  : Waytek wire tool #533, for crimping ECU pins :: http://order.waytekwire.com/productdetail2/M37/533/CRIMPER,%20SEALED%20METRI-PACK/  : Delphi Metri-Pack pin re…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="272" xml:space="preserve">= Useful Tools =

: Waytek wire tool #533, for crimping ECU pins
:: http://order.waytekwire.com/productdetail2/M37/533/CRIMPER,%20SEALED%20METRI-PACK/

: Delphi Metri-Pack pin removal tool
:: http://www.bmotorsports.com/shop/product_info.php/cPath/111_113/products_id/1083</text>
    <sha1>d94b219ee77d6f23debc1569cfcf118de51ff8e9</sha1>
  </revision>
  <revision>
    <id>879</id>
    <timestamp>2009-11-29T18:38:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="254" xml:space="preserve">: Waytek wire tool #533, for crimping ECU pins
:: http://order.waytekwire.com/productdetail2/M37/533/CRIMPER,%20SEALED%20METRI-PACK/

: Delphi Metri-Pack pin removal tool
:: http://www.bmotorsports.com/shop/product_info.php/cPath/111_113/products_id/1083</text>
    <sha1>1539636ff85a6bbbd5ddc0bb143b47eee26c6117</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>Plugs, Pins, and Connectors</title>
  <ns>0</ns>
  <id>242</id>
  <revision>
    <id>882</id>
    <parentid>881</parentid>
    <timestamp>2009-11-29T18:38:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '= Evo VIII and 2g DSM =  This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doe…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2475" xml:space="preserve">= Evo VIII and 2g DSM =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND</text>
    <sha1>cbe5390ea3abdf3ed13c2ef2580317093afa19f9</sha1>
  </revision>
  <revision>
    <id>884</id>
    <parentid>881</parentid>
    <timestamp>2009-11-30T16:12:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add more connectors.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3565" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these.</text>
    <sha1>4bf9e458c3eeec40536d79a600b3aa9aa76c5632</sha1>
  </revision>
  <revision>
    <id>885</id>
    <parentid>881</parentid>
    <timestamp>2009-11-30T16:17:17Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost Control Solenoid / EGR */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3704" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger carries the [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 female plug, pins, and seals].</text>
    <sha1>11ecaadcc0fd3a1b7db5a8514c93a1485632c03d</sha1>
  </revision>
  <revision>
    <id>886</id>
    <parentid>881</parentid>
    <timestamp>2009-11-30T16:21:10Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost Control Solenoid / EGR */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4135" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals].</text>
    <sha1>4d59119030ee27e0c4aeedccb7936300e538baca</sha1>
  </revision>
  <revision>
    <id>887</id>
    <parentid>881</parentid>
    <timestamp>2009-11-30T16:21:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost Control Solenoid / EGR */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4221" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>84abf230bcee8e95b989ec61c9523b2c0d3186e1</sha1>
  </revision>
  <revision>
    <id>888</id>
    <parentid>881</parentid>
    <timestamp>2009-11-30T16:22:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4306" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins. Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes them available].

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>e4e38678da4e33c25756b25cfe1a61dbbab984e9</sha1>
  </revision>
  <revision>
    <id>899</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T20:26:14Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4307" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].  Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>1453bb18dbf8bf85db7f3f2124ba5116a36c91af</sha1>
  </revision>
  <revision>
    <id>889</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T20:47:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo IX ECU */ more info about pins, add links to plug datasheets.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4564" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].  Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available]. Each plug has a block of 6 large pins, with the remainder being the small type.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; apparently, [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>e65524c441645974419d111caacd609c7bb3216d</sha1>
  </revision>
  <revision>
    <id>883</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T20:48:10Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4568" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

''Plugs:''
: 12 pin male, '''917978'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND


= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].  Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available]. Each plug has a block of 6 large pins, with the remainder being the small type.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>b2004fc1099e074c1ca41fa62a32ad57a87483a2</sha1>
  </revision>
  <revision>
    <id>890</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T21:01:36Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo VIII and 2g DSM ECU */ Add datasheet links for plugs, and information about large vs. small pins.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5590" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors].  Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available]. Each plug has a block of 6 large pins, with the remainder being the small type.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])</text>
    <sha1>19fb8c81fdd28325b77817aeae2f0449a321ac4a</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>ECU Development</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>662</id>
    <parentid>658</parentid>
    <timestamp>2009-11-29T18:41:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="517" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[ECU Wiring]]
** [[USDM VIII ECU Pinout]]
** [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]

== Communications ==

* [[MUT_Requests]]
* [[MUT_Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>2d8476717183ae8d11bf3f2bb426c1d23c1e78a0</sha1>
  </revision>
  <revision>
    <id>648</id>
    <parentid>647</parentid>
    <timestamp>2009-11-29T18:41:44Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="498" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]

== Communications ==

* [[MUT_Requests]]
* [[MUT_Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>5944c1f8416e0e8651a1b9fbdf57e3079e59cf50</sha1>
  </revision>
  <revision>
    <id>649</id>
    <parentid>647</parentid>
    <timestamp>2009-11-29T18:41:57Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Communications */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="498" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>654c21b1b94b48d5c8934034abf33a1a43641040</sha1>
  </revision>
  <revision>
    <id>652</id>
    <parentid>647</parentid>
    <timestamp>2009-11-30T02:05:03Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="516" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>1e562abd0eea278533fbdc160907a2b0166bfa4d</sha1>
  </revision>
  <revision>
    <id>653</id>
    <parentid>647</parentid>
    <timestamp>2009-11-30T15:25:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="572" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[media:Openport13.pdf|OpenPort 1.3 Schematic]] (PDF)
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>fb784af6445c73c3f7c7a32bb74b03d9a494c9db</sha1>
  </revision>
  <revision>
    <id>654</id>
    <parentid>647</parentid>
    <timestamp>2009-11-30T21:42:34Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="600" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* [[media:Openport13.pdf|OpenPort 1.3 Schematic]] (PDF)
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>ab826cc69c804ebe9ac5123fdc618f74f9fb182f</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>MUT Requests</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>818</id>
    <parentid>808</parentid>
    <timestamp>2009-11-30T01:39:07Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>More acamus A/T additions.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8483" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|AirTemp
|Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|52
|
|
|Rear Long Fuel Trim Bank 1
|
|
|
|-
|53
|
|
|Rear Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|60
|
|
|Rear O2 Trim - Low
|
|
|
|-
|61
|
|
|Rear O2 Trim - Mid
|
|
|
|-
|62
|
|
|Rear O2 Trim - High
|
|
|
|-
|63
|
|
|Rear O2 Feedback Trim
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|96
|
|MAF_ADC
|RAW MAF ADC value 
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A8
|
|ATInShaftPulse
|Input shaft speed pulse (A/T)
|On/Off
|x bit 1
|
|-
|A8
|
|ATOutShaftPulse
|Output shaft speed pulse (A/T)
|On/Off
|x bit 2
|
|-
|A8
|
|ATGearL
|Gear: Low (A/T)
|On/Off
|x bit 32
|
|-
|A8
|
|ATGear2
|Gear: 2 (A/T)
|On/Off
|x bit 64
|
|-
|A8
|
|ATGear3
|Gear: 3 (A/T)
|On/Off
|x bit 128
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B3
|
|ATGearNeutral
|Gear: Neutral (A/T)
|On/Off
|x bit 1
|
|-
|B3
|
|ATGearDrive
|Gear: Drive (A/T)
|On/Off
|x bit 2
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|}
&lt;/center&gt;</text>
    <sha1>e86aabe24837be16fec54f8c199d604a1ef01cdd</sha1>
  </revision>
  <revision>
    <id>812</id>
    <parentid>808</parentid>
    <timestamp>2009-12-14T01:50:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8500" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!MUT Value (0x....)
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|UnscaledAirTemp
|Unscaled Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|52
|
|
|Rear Long Fuel Trim Bank 1
|
|
|
|-
|53
|
|
|Rear Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|60
|
|
|Rear O2 Trim - Low
|
|
|
|-
|61
|
|
|Rear O2 Trim - Mid
|
|
|
|-
|62
|
|
|Rear O2 Trim - High
|
|
|
|-
|63
|
|
|Rear O2 Feedback Trim
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|96
|
|MAF_ADC
|RAW MAF ADC value 
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A8
|
|ATInShaftPulse
|Input shaft speed pulse (A/T)
|On/Off
|x bit 1
|
|-
|A8
|
|ATOutShaftPulse
|Output shaft speed pulse (A/T)
|On/Off
|x bit 2
|
|-
|A8
|
|ATGearL
|Gear: Low (A/T)
|On/Off
|x bit 32
|
|-
|A8
|
|ATGear2
|Gear: 2 (A/T)
|On/Off
|x bit 64
|
|-
|A8
|
|ATGear3
|Gear: 3 (A/T)
|On/Off
|x bit 128
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B3
|
|ATGearNeutral
|Gear: Neutral (A/T)
|On/Off
|x bit 1
|
|-
|B3
|
|ATGearDrive
|Gear: Drive (A/T)
|On/Off
|x bit 2
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|}
&lt;/center&gt;</text>
    <sha1>30c1c71d15310f43713b856062e39cd60b14605d</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>File:OBD-connector-pinout.png</title>
  <ns>6</ns>
  <id>238</id>
  <revision>
    <id>859</id>
    <parentid>858</parentid>
    <timestamp>2009-11-30T02:01:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[File:OBD-connector-pinout.png]]":&amp;#32;OBD-II connector picture from the factory service manual.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">OBD-II connector pinout, taken from [http://en.wikipedia.org/wiki/File:OBD-connector-pinout.png Wikipedia] (released into the public domain).</text>
    <sha1>332e31623652eaf861e9f6b6db0d525dd20d041e</sha1>
  </revision>
  <revision>
    <id>861</id>
    <parentid>860</parentid>
    <timestamp>2009-11-30T02:25:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[File:OBD-connector-pinout.png]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">OBD-II connector pinout, taken from [http://en.wikipedia.org/wiki/File:OBD-connector-pinout.png Wikipedia] (released into the public domain).</text>
    <sha1>332e31623652eaf861e9f6b6db0d525dd20d041e</sha1>
  </revision>
  <revision>
    <id>860</id>
    <parentid>859</parentid>
    <timestamp>2009-11-30T02:25:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">OBD-II connector pinout, from the factory service manual.</text>
    <sha1>a35c921450cf6679a365181365bedd20f6c7b126</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>File:Diag-connector.png</title>
  <ns>6</ns>
  <id>243</id>
  <revision>
    <id>925</id>
    <timestamp>2009-11-30T02:02:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Diagnostic connector from the factory service manual.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">Diagnostic connector from the factory service manual.</text>
    <sha1>1cbb5786de657731c5afbb857a681fd5f8c151d8</sha1>
  </revision>
  <revision>
    <id>926</id>
    <parentid>925</parentid>
    <timestamp>2009-11-30T02:26:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>uploaded a new version of "[[File:Diag-connector.png]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">Diagnostic connector from the factory service manual.</text>
    <sha1>1cbb5786de657731c5afbb857a681fd5f8c151d8</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>Diag Pinout</title>
  <ns>0</ns>
  <id>244</id>
  <revision>
    <id>927</id>
    <timestamp>2009-11-30T02:05:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '[[Image:Diag-connector.png]]  {| border=1 cellspacing=0 cellpadding=5 |21||Traction – TCL/4WD  |- |22||Steering - 4WS/ECPS  |- |25||ECU |- |26||ECU programing |- |27||Transmiss…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="231" xml:space="preserve">[[Image:Diag-connector.png]]

{| border=1 cellspacing=0 cellpadding=5
|21||Traction – TCL/4WD 
|-
|22||Steering - 4WS/ECPS 
|-
|25||ECU
|-
|26||ECU programing
|-
|27||Transmission ECU programming
|-
|32||Adapter identification
|}</text>
    <sha1>3826cacbba59738b050fdbe36aee108947a21521</sha1>
  </revision>
  <revision>
    <id>928</id>
    <parentid>927</parentid>
    <timestamp>2009-11-30T02:05:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="285" xml:space="preserve">[[Image:Diag-connector.png]]

{| border=1 cellspacing=0 cellpadding=5
|21||Traction – TCL/4WD 
|-
|22||Steering - 4WS/ECPS 
|-
|23||
|-
|24||
|-
|25||ECU
|-
|26||ECU programing
|-
|27||Transmission ECU programming
|-
|28||
|-
|29||
|-
|30||
|-
|31||
|-
|32||Adapter identification
|}</text>
    <sha1>f4a5775ef2b8358dc6b7e12b28a9158d5fbfdb46</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>OBD Pinout</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>851</id>
    <parentid>850</parentid>
    <timestamp>2009-11-30T02:06:15Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="596" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0 cellpadding=5
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Gnd
|-
| 5||Gnd
|-
| 6||Transmission - ELC-4/5AT 
|-
| 7||К-Line (ISO 9141) 
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|}</text>
    <sha1>068ce7b2245a9016757ef8f64f6afec6ec924fbf</sha1>
  </revision>
  <revision>
    <id>853</id>
    <parentid>850</parentid>
    <timestamp>2009-11-30T02:49:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="611" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0 cellpadding=5
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Gnd
|-
| 5||Gnd
|-
| 6||Transmission - ELC-4/5AT 
|-
| 7||К-Line (ISO 9141) - ECU, ABS, SRS
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|}</text>
    <sha1>4d4422d670c1d6e596591d620bf8e481e5e2631d</sha1>
  </revision>
  <revision>
    <id>855</id>
    <parentid>850</parentid>
    <timestamp>2009-11-30T15:21:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="669" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0 cellpadding=5
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Chassis ground
|-
| 5||Signal ground
|-
| 6||Transmission - ELC-4/5AT
(CAN high; ISO 15765-4 and SAE-J2284)
|-
| 7||К-Line (ISO 9141) - ECU, ABS, SRS
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal 
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|}</text>
    <sha1>a90356db9e5dc2d7138987520355479bbbc41c39</sha1>
  </revision>
  <revision>
    <id>857</id>
    <parentid>850</parentid>
    <timestamp>2009-11-30T15:21:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="705" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0 cellpadding=5
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Chassis ground
|-
| 5||Signal ground
|-
| 6||Transmission - ELC-4/5AT
(CAN high; ISO 15765-4 and SAE-J2284)
|-
| 7||К-Line (ISO 9141) - ECU, ABS, SRS
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal
(CAN low; ISO 15765-4 and SAE-J2284)
|-
|15||L-line (ISO 9141)
|-
|16||Power supply +12V
|}</text>
    <sha1>d1b0b3f037ed3130269bcbce4fc6db114c8121c4</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>File:Openport13.pdf</title>
  <ns>6</ns>
  <id>245</id>
  <revision>
    <id>929</id>
    <timestamp>2009-11-30T15:22:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Schematic for the OpenPort 1.3 USB&lt;-&gt;OBD-II interface.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54" xml:space="preserve">Schematic for the OpenPort 1.3 USB&lt;-&gt;OBD-II interface.</text>
    <sha1>902117c6d8ee5c55f4a75032ebca52b93a72d8b3</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>Logging Cable</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>324</id>
    <parentid>322</parentid>
    <timestamp>2009-11-30T20:04:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1616" xml:space="preserve">There are a few cables that can be used to log and reflash data from the evo.  

There have been a number of cables that can reflash and datalog Mitsubishi Vehicles.

OpenPort 1.0 (no longer available)

OpenPort 1.2 (no longer available)

OpenPort 1.3M (no longer available)

OpenPort 1.3D (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables] $57  
  - Datalogging support EvoScan v2.6 - 1994-2008 Mitsubishi Datalogging support (excluding EvoX).
  - No reflashing support, this is a pure datalogging only cable.

OpenPort 1.3R (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables] $97 
  - Datalogging support EvoScan v2.6 - 1994-2007(Evo4-9) Mitsubishi Datalogging support.
  - Same cable as OpenPort 1.3U except it does not include EcuFlash serial license.
  - Reflash rom supported only via EvoScan software for Evo 7/8 vehicles. 

OpenPort 1.3U (only available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables]) $137
  - Supports the Latest EcuFlash v1.42 - Evo 7/8/9 flashing support.
  - Supports the latest EvoScan - Evo 7/8 flashing support. 1994-2007(Evo4-9) Mitsubishi Datalogging support.

OpenPort 2.0 (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables] $169  or [http://www.tactrix.com tactrix.com] $189)
  - Supports the Latest EcuFlash v1.42 - Evo 5/6/7/8/9/10 flashing support.
  - Datalogging support EvoScan v2.6 - 1994-2009 Mitsubishi Datalogging support including EvoX.

See [[ECU Development]] for schematics for the OpenPort 1.3U cable, as well as pinouts for the Evo ECUs, OBD-II, and diag plugs.</text>
    <sha1>4f231883942501a5d2ebf6a5bc3b49d7c1a69f56</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>File:ADC-evo8-harness.jpg</title>
  <ns>6</ns>
  <id>246</id>
  <revision>
    <id>930</id>
    <timestamp>2009-11-30T21:15:08Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>[[Map switching harness]] for the Evo VIII</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42" xml:space="preserve">[[Map switching harness]] for the Evo VIII</text>
    <sha1>fc2963ff144b12d6391f5a750995a4fd19b990cc</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>File:ADC-evo9-harness.png</title>
  <ns>6</ns>
  <id>247</id>
  <revision>
    <id>931</id>
    <timestamp>2009-11-30T21:16:32Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>[[Map switching harness]] for the Evo IX.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">[[Map switching harness]] for the Evo IX.</text>
    <sha1>f7210123c0d8956021bb10bbc53eef3790ea7eb0</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>Map switching harness</title>
  <ns>0</ns>
  <id>248</id>
  <revision>
    <id>932</id>
    <timestamp>2009-11-30T21:40:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a s…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7499" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [[http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses; for many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for pin #42 on the ECU harness.
:: Evo IX: '''small''' pin, for pin #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>5dd136e6da1d2ebe6274e92e76f80cb3e762e106</sha1>
  </revision>
  <revision>
    <id>938</id>
    <parentid>934</parentid>
    <timestamp>2009-11-30T21:46:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7499" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [[http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for pin #42 on the ECU harness.
:: Evo IX: '''small''' pin, for pin #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>13a7b57e340c9427a3ef162a4172ff147ca4af94</sha1>
  </revision>
  <revision>
    <id>937</id>
    <parentid>934</parentid>
    <timestamp>2009-11-30T21:46:32Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>/* Parts List */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7509" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [[http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for position #42 on the ECU harness.
:: Evo IX: '''small''' pin, for position #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>f6cf96d548cdf60d2ed6f5c7686293c707fa4f32</sha1>
  </revision>
  <revision>
    <id>936</id>
    <parentid>934</parentid>
    <timestamp>2009-11-30T21:54:52Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Instructions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8177" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [[http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for position #42 on the ECU harness.
:: Evo IX: '''small''' pin, for position #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Pin removal ==

Thanks to mrfred for this [http://forums.evolutionm.net/5191835-post379.html fantastic writeup] on the process of removing pins from the IX harness. Essentially, pull back the retaining clip ("secondary restraint), and the pins should come out easily with a tug.

See these two posts ([http://forums.evolutionm.net/5107038-post122.html 1] and [http://forums.evolutionm.net/5107038-post123.html 2]) from Richard L. (Aquamist) for an example of how to unlock the pins on a VIII harness. Basically, lift the white strip from the plug approximately 1/16" with a very small, flat-tipped screwdriver, and the pin you want to remove should pop right out.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>fd0f1ea5aad16fa5edb324f55a926c6333537579</sha1>
  </revision>
  <revision>
    <id>933</id>
    <parentid>932</parentid>
    <timestamp>2009-12-09T16:36:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>typo fix</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8176" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for position #42 on the ECU harness.
:: Evo IX: '''small''' pin, for position #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Pin removal ==

Thanks to mrfred for this [http://forums.evolutionm.net/5191835-post379.html fantastic writeup] on the process of removing pins from the IX harness. Essentially, pull back the retaining clip ("secondary restraint), and the pins should come out easily with a tug.

See these two posts ([http://forums.evolutionm.net/5107038-post122.html 1] and [http://forums.evolutionm.net/5107038-post123.html 2]) from Richard L. (Aquamist) for an example of how to unlock the pins on a VIII harness. Basically, lift the white strip from the plug approximately 1/16" with a very small, flat-tipped screwdriver, and the pin you want to remove should pop right out.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>a9227b41b15bba45452e4f96ab0c69b10d6c6d4e</sha1>
  </revision>
</page>
<page arvcontinue="20091129183605|864">
  <title>EvoEcu:Copyrights</title>
  <ns>4</ns>
  <id>249</id>
  <revision>
    <id>939</id>
    <timestamp>2009-12-30T20:21:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'Please see http://creativecommons.org/licenses/by-sa/3.0/ for the short version, or http://creativecommons.org/licenses/by-sa/3.0/legalcode for the legal details.'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="162" xml:space="preserve">Please see http://creativecommons.org/licenses/by-sa/3.0/ for the short version, or http://creativecommons.org/licenses/by-sa/3.0/legalcode for the legal details.</text>
    <sha1>f2188dfae7fe6229f99c95e51db44fa9726f0475</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>USDM VIII ECU Pinout</title>
  <ns>0</ns>
  <id>239</id>
  <revision>
    <id>867</id>
    <parentid>866</parentid>
    <timestamp>2010-01-05T21:13:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Complete harness */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5512" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 25, 26, 71, 80, 81, 82, 91, and 92 (16 total) are "large"; the remaining (60) pins are "small". Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}
|}

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|1||2||3||4||5||6||7||8||9||10||11||12||13
|-
|14||15||16||17||18||19||20||21||22||23||24||25||26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||73||74||75||76||77||78||79||80||81
|-
|82||83||84||85||86||87||88||89||90||91||92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>4552b3ec687f1b380872b594a12929b39a65a29c</sha1>
  </revision>
  <revision>
    <id>868</id>
    <parentid>866</parentid>
    <timestamp>2010-01-05T21:13:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6040" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 25, 26, 71, 80, 81, 82, 91, and 92 (16 total) are "large"; the remaining (60) pins are "small". Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}
|}

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor signal
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor signal
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor heater control
|-
| 76||Front O2 sensor heater control
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>618d4bab52b1c6dfc82439b97eff10fbf0f4baa0</sha1>
  </revision>
  <revision>
    <id>871</id>
    <parentid>866</parentid>
    <timestamp>2010-01-10T16:31:35Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Front/Rear O2 sensor and heater pins were swapped accidentally. Fixed.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6040" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 25, 26, 71, 80, 81, 82, 91, and 92 (16 total) are "large"; the remaining (60) pins are "small". Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}
|}

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor heater control
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor heater control
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-14)
|}


= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor signal
|-
| 76||Front O2 sensor signal
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>affb909cbb59b57cf88645354415d3d95e2700e4</sha1>
  </revision>
  <revision>
    <id>863</id>
    <timestamp>2010-01-15T19:09:28Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* C-117 */ Add note about pin 56 being OBD-II pine 1, and note that pin 62 is the OBD-II K-line.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6107" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 25, 26, 71, 80, 81, 82, 91, and 92 (16 total) are "large"; the remaining (60) pins are "small". Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}
|}

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor heater control
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||Data link (OBD-II/MUT-III comms, pin 1 on OBD-II port, C-14)
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor heater control
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, K-line, pin 7 on OBD-II port, C-14)
|}

= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor signal
|-
| 76||Front O2 sensor signal
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>1a6ff007fa429fd348186d849c8e99934ecd43f8</sha1>
  </revision>
  <revision>
    <id>866</id>
    <parentid>863</parentid>
    <timestamp>2010-01-15T21:17:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* C-117 */ Pin 56 is a 2g DSM thing.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6047" xml:space="preserve">The USDM Evo VIII ECU uses a four-plug harness, with two rows of pins for each plug. The factory service manual refers to these plugs as C-121, C-119, C-117, and C-115.

For a picture of the ECU-side of the harness, see [http://www.roadraceengineering.com/evo/tech/EVO-ecuwiring.htm Road Race Engineering's EVO VIII pinout page].

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 25, 26, 71, 80, 81, 82, 91, and 92 (16 total) are "large"; the remaining (60) pins are "small". Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}
|}

= C-121 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #3
|-
|  3||Fuel pressure solenoid
|-
|  4||Idle air control motor, coil A1
|-
|  5||Idle air control motor, coil B1
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||A/C compressor clutch control, ground
|-
|  9||Evaporative emission purge solenoid
|-
| 10||Ignition coil, cylinder #1 and #4
|-
| 11||Turbocharger wastegate solenoid
|-
| 12||12V power (through MFI relay)
|-
| 13||Chassis ground
|-
| 14||Injector #2
|-
| 15||Injector #4
|-
| 16||
|-
| 17||Idle air control motor, coil A2
|-
| 18||Idle air control motor, coil B2
|-
| 19||Volume airflow sensor reset (MAF filter?)
|-
| 20||
|-
| 21||A/C condenser fan control
|-
| 22||Fuel pump relay
|-
| 23||Ignition coil, cylinder #2 and #3
|-
| 24||A/C control (?)
|-
| 25||12V power (through MFI relay)
|-
| 26||Chassis ground
|}


= C-119 =

{| border=1 cellspacing=0 style="text-align: center"
|31||32||33||34||35||36||37||38
|-
|39||40||41||42||43||44||45||46
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 31||
|-
| 32||A/C condenser fan relay (high)
|-
| 33||Alternator voltage regulator, ground
|-
| 34||A/C condenser fan relay (low)
|-
| 35||Charge air cooler water spray fluid meter
|-
| 36||Check-engine light
|-
| 37||Power steering pressure sensor signal
|-
| 38||MFI relay control, ground
|-
| 39||Fuel pump relay control, ground
|-
| 40||Sensor ground (IAT, cam position, fuel tank pressure, MDP, TPS)
|-
| 41||Alternator voltage regulator signal
|-
| 42||'''Aftermarket use:''' ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 43||Clutch pedal position switch
|-
| 44||Charge air cooler water spray switch (auto control)
|-
| 45||A/C control (?)
|-
| 46||Fuel level sender signal (gauge)
|}


= C-117 =

{| border=1 cellspacing=0 style="text-align: center"
|51||52||53||54||55||56
|-
|57||58||59||60||61||62
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 51||Engine immobilizer system
|-
| 52||
|-
| 53||
|-
| 54||Rear O2 sensor heater control
|-
| 55||Evaporative emission ventilation solenoid
|-
| 56||
|-
| 57||Charge air cooler water spray relay control
|-
| 58||Engine speed (RPM)
|-
| 59||
|-
| 60||Front O2 sensor heater control
|-
| 61||Fuel tank differential pressure sensor signal
|-
| 62||Data link (OBD-II/MUT-III comms, K-line, pin 7 on OBD-II port, C-14)
|}

= C-115 =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|71||72||73||74||75||76||77||78||79||style="background-color: yellow"|80||style="background-color: yellow"|81
|-
|style="background-color: yellow"|82||83||84||85||86||87||88||89||90||style="background-color: yellow"|91||style="background-color: yellow"|92
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Starter relay signal
|-
| 72||Intake air temperature sensor signal
|-
| 73||MAP sensor signal
|-
| 74||Fuel level sender signal (low-fuel light)
|-
| 75||Rear O2 sensor signal
|-
| 76||Front O2 sensor signal
|-
| 77||Fuel temperature sensor signal
|-
| 78||Knock sensor signal
|-
| 79||Data link (flash signal, pin 26 on diagnostic port, C-15)
|-
| 80||12V power (backup ECU power, wired directly from battery)
|-
| 81||Throttle position sensor power (+5V)
|-
| 82||Ignition switch IG1 (power when ignition in postion "ON" and "START")
|-
| 83||Coolant temperature sensor signal
|-
| 84||Throttle position sensor signal
|-
| 85||MAF barometric pressure sensor signal
|-
| 86||Vehicle speed sensor signal
|-
| 87||
|-
| 88||Intake cam position sensor signal
|-
| 89||Crankshaft position sensor signal
|-
| 90||MAF sensor signal
|-
| 91||Charge air cooler water spray switch (manual control)
|-
| 92||Sensor ground (O2 heaters, coolant temp, tps signal, MAP, fuel tank pressure signal)
|}</text>
    <sha1>96eefc6189e93009693eb50b9532f813407a2b6b</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Plugs, Pins, and Connectors</title>
  <ns>0</ns>
  <id>242</id>
  <revision>
    <id>891</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T21:22:08Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6003" xml:space="preserve">= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>bef5d969ad9c9ea4efd313fec7ac4d2967132da0</sha1>
  </revision>
  <revision>
    <id>892</id>
    <parentid>881</parentid>
    <timestamp>2010-01-05T22:21:28Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added preliminary speculation on DSM connectors.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7307" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

There are several pin options. More to come later.

= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>62c36eb1e0a81b77f99b312cc12e3146203e537e</sha1>
  </revision>
  <revision>
    <id>893</id>
    <parentid>881</parentid>
    <timestamp>2010-01-06T15:53:58Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* 1g DSM ECU */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8112" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>efa19c2d282ef194f2e1cb8dc88712dd915758b4</sha1>
  </revision>
  <revision>
    <id>894</id>
    <parentid>881</parentid>
    <timestamp>2010-01-06T15:55:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo VIII and 2g DSM ECU */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8122" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses Multilock 040/070-Series Hybrid Plugs from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)]. [http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>1389f865c374f436634483d4c49421e8d0a4c0f4</sha1>
  </revision>
  <revision>
    <id>895</id>
    <parentid>881</parentid>
    <timestamp>2010-01-06T16:28:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo VIII and 2g DSM ECU */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8303" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>c41b703480e530bb7e71564517d89c70775eb6d5</sha1>
  </revision>
  <revision>
    <id>916</id>
    <parentid>881</parentid>
    <timestamp>2010-01-11T22:51:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8403" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" connector is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation])

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector, and the pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>d4c7c7bcb739752cb0799d512776f3d0960fdcae</sha1>
  </revision>
  <revision>
    <id>896</id>
    <parentid>881</parentid>
    <timestamp>2010-01-11T23:02:52Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8434" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>3a080cccd990e2c81fdc0a746f8b418d019787e1</sha1>
  </revision>
  <revision>
    <id>897</id>
    <parentid>881</parentid>
    <timestamp>2010-01-12T04:07:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8493" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs and Evos I-III also used this physical connector for the MUT scantool, but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>3a3762523123d7e96d389ce657ac42a66f78b27d</sha1>
  </revision>
  <revision>
    <id>898</id>
    <parentid>881</parentid>
    <timestamp>2010-01-12T04:12:04Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8591" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>48d992a2235b7039c441b35a5e1fb81cc31e3b4f</sha1>
  </revision>
  <revision>
    <id>900</id>
    <parentid>881</parentid>
    <timestamp>2010-01-18T04:47:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add part numbers for OBD-II connectors.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9365" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>8f3d9cc1db1bc564183215a3a4bbd784ba21cbd9</sha1>
  </revision>
  <revision>
    <id>901</id>
    <parentid>881</parentid>
    <timestamp>2010-01-19T22:39:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9512" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>4005cebbde701a89eb8b9d8e812cb6eb467d2660</sha1>
  </revision>
  <revision>
    <id>902</id>
    <parentid>881</parentid>
    <timestamp>2010-01-19T23:22:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9877" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

'''Untested:''' this might also be from the HD line:

http://www.sws.co.jp/en/product/connector/nwp_hd.html

Compare [http://swsct.sws.co.jp/components/en/housing.asp?number_s=60980251hd HD] to [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt MT]; it's still a 090 terminal (pin), and the physical footprint and pin layout looks very similar.

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>1dc3a35fa474aeb53562ee280684e4cef794a6b9</sha1>
  </revision>
  <revision>
    <id>903</id>
    <parentid>881</parentid>
    <timestamp>2010-01-20T04:40:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9737" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

'''Another option!''' This appears to be a [http://www.mcausa.com/ Mitsubishi Cable America] [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. Sourcing this part is currently left as an exercise to the reader.

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].</text>
    <sha1>e9cdc50b7bbf270690bf31e743783277b9d9b472</sha1>
  </revision>
  <revision>
    <id>907</id>
    <parentid>881</parentid>
    <timestamp>2010-03-07T01:20:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost Control Solenoid / EGR */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9966" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

'''Another option!''' This appears to be a [http://www.mcausa.com/ Mitsubishi Cable America] [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. Sourcing this part is currently left as an exercise to the reader.

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.</text>
    <sha1>c88f40f2dbdace3b7474f3ab6254f6c7a7a4f04a</sha1>
  </revision>
  <revision>
    <id>908</id>
    <parentid>881</parentid>
    <timestamp>2010-03-07T01:25:01Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Diagnostic Connector */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10395" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]. No, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. 

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.</text>
    <sha1>59a76b964a0c13a8b963845eaddb2652ee715433</sha1>
  </revision>
  <revision>
    <id>913</id>
    <parentid>881</parentid>
    <timestamp>2010-05-03T21:27:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add ACD information.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11070" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]. No, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. 

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.</text>
    <sha1>7bf2c62ecd825f8a2370c05126edc772871078cd</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>USDM IX ECU Pinout</title>
  <ns>0</ns>
  <id>240</id>
  <revision>
    <id>873</id>
    <parentid>872</parentid>
    <timestamp>2010-01-06T15:27:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Add pin counts.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7533" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= Complete harness - 93-pin interface =

Pins 1, 2, 9, 10, 24, 25, 46, 47, 58, 59, 67, 68, 76, 77, 89, 90, 99, and 100 are the "large" variety (so, 6 per plug, or 18 total pins are large), and the remainder (29, 22, and 24 pins for each plug, or 75 total) are the "small" type. The large pins have been colored in yellow in the diagrams below.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}
|}


= C-121 - 35-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 - 28-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 - 30-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>47fab5d187323e81fb77c388b45196afd750b80c</sha1>
  </revision>
  <revision>
    <id>878</id>
    <parentid>873</parentid>
    <timestamp>2010-01-14T20:48:52Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7682" xml:space="preserve">The USDM Evo IX ECU uses a three-plug harness, with three rows of pins for each plug.  The factory service manual refers to these plugs as C-121, C-119, and C-117.

= PCB Pictures =

[http://www.flickr.com/photos/edward_marshall/4243664618/ Front], [http://www.flickr.com/photos/edward_marshall/4243665436/ Back]

= Complete harness - 93-pin interface =

Pins 1, 2, 9, 10, 24, 25, 46, 47, 58, 59, 67, 68, 76, 77, 89, 90, 99, and 100 are the "large" variety (so, 6 per plug, or 18 total pins are large), and the remainder (29, 22, and 24 pins for each plug, or 75 total) are the "small" type. The large pins have been colored in yellow in the diagrams below.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-119!!C-117
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}
|}


= C-121 - 35-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: black"| ||3||4||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||5||6||style="background-color: black"| ||7||8
|-
|style="background-color: yellow"|9||style="background-color: yellow"|10||11||12||13||14||15||16||17||18||19||20||21||22||23
|-
|style="background-color: yellow"|24||style="background-color: yellow"|25||style="background-color: black"| ||26||27||28||29||style="background-color: black"| ||30||31||32||33||style="background-color: black"| ||34||35
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
|  1||Injector #1
|-
|  2||Injector #4
|-
|  3||Front O2 heater control
|-
|  4||
|-
|  5||
|-
|  6||Exhaust gas recirculation solenoid relay control, ground
|-
|  7||
|-
|  8||Alternator voltage regulator, ground
|-
|  9||Injector #2
|-
| 10||
|-
| 11||Ignition coil, cylinder #1 and #4
|-
| 12||Ignition coil, cylinder #2 and #3
|-
| 13||
|-
| 14||Idle stepping motor (A)
|-
| 15||Idle stepping motor (B)
|-
| 16||Evaporative purge solenoid relay control, ground
|-
| 17||
|-
| 18||Cooling fan relay control, ground
|-
| 19||AFS active filter (MAF signal filter?)
|-
| 20||A/C compressor clutch relay control, ground
|-
| 21||Fuel pump relay control, ground
|-
| 22||Check-engine light control, ground
|-
| 23||
|-
| 24||Injector #3
|-
| 25||
|-
| 26||Rear O2 heater control
|-
| 27||
|-
| 28||Idle stepping motor (C)
|-
| 29||Idle stepping motor (C)
|-
| 30||A/C condenser fan relay control, high
|-
| 31||A/C condenser fan relay control, low
|-
| 32||MIVEC valve control
|-
| 33||
|-
| 34||General sensor ground
|-
| 35||Evaporative ventilation solenoid relay control, ground
|-
|}


= C-119 - 28-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|41||42||43||44||style="background-color: black"| ||colspan=3| ||style="background-color: black"| ||45||style="background-color: yellow"|46||style="background-color: yellow"|47
|-
|48||49||50||51||52||53||54||55||56||57||style="background-color: yellow"|58||style="background-color: yellow"|59
|-
|60||61||style="background-color: black"| ||62||63||64||style="background-color: black"| ||65||66||style="background-color: black"| ||style="background-color: yellow"|67||style="background-color: yellow"|68
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 41||Wastegate solenoid relay control, ground
|-
| 42||Throttle position sensor power (+5V)
|-
| 43||Crankshaft position sensor signal
|-
| 44||Coolant temperature sensor signal
|-
| 45||Engine speed (RPM)
|-
| 46||Chassis ground
|-
| 47||12V power (through MFI relay)
|-
| 48||Fuel pressure solenoid control, ground
|-
| 49||Sensor ground (O2, MAP, air temp, coolant, TPS)
|-
| 50||Exhaust camshaft position sensor signal
|-
| 51||MAF barometric pressure sensor signal
|-
| 52||Alternator voltage regulator signal
|-
| 53||Intake camshaft position sensor signal
|-
| 54||Power steering pressure sensor signal
|-
| 55||Fuel pump relay control, ground
|-
| 56||
|-
| 57||MFI relay control, ground
|-
| 58||Chassis ground
|-
| 59||12V power (through MFI relay)
|-
| 60||12V power (backup ECU power, wired directly from battery)
|-
| 61||MAF sensor signal
|-
| 62||Intake air temperature sensor signal
|-
| 63||
|-
| 64||'''Aftermarket use''': ADC 0F, typically used for map switching in [[TephraMod]]
|-
| 65||Air conditioning control
|-
| 66||
|-
| 67||
|-
| 68||Starter relay signal
|}


= C-117 - 30-pin connector =

{| border=1 cellspacing=0 style="text-align: center"
|71||72||style="background-color: black"| ||73||74||style="background-color: black"| ||colspan=3|JAE||style="background-color: black"| ||75||style="background-color: yellow"|76||style="background-color: yellow"|77
|-
|78||79||80||81||82||83||84||85||86||87||88||style="background-color: yellow"|89||style="background-color: yellow"|90
|-
|91||92||93||style="background-color: black"| ||94||95||style="background-color: black"| ||96||97||98||style="background-color: black"| ||style="background-color: yellow"|99||style="background-color: yellow"|100
|}


{| border=1 cellpadding=5 cellspacing=0
!Pin!!Description
|-
| 71||Front O2 sensor signal
|-
| 72||
|-
| 73||Rear O2 sensor signal
|-
| 74||
|-
| 75||
|-
| 76||
|-
| 77||
|-
| 78||Throttle position sensor signal
|-
| 79||
|-
| 80||Vehicle speed sensor signal
|-
| 81||
|-
| 82||
|-
| 83||Air conditioning control
|-
| 84||
|-
| 85||Data link (OBD-II/MUT-III comms, pin 7 on OBD-II port, C-122)
|-
| 86||
|-
| 87||
|-
| 88||Clutch pedal switch
|-
| 89||
|-
| 90||
|-
| 91||Knock sensor signal
|-
| 92||MAP sensor signal
|-
| 93||Fuel tank pressure differential sensor signal
|-
| 94||
|-
| 95||Fuel level sender sensor signal (gauge)
|-
| 96||Fuel temperature sensor signal
|-
| 97||Fuel level sender sensor signal (low-fuel light)
|-
| 98||Engine immobilizer system
|-
| 99||Ignition switch IG1 (power when ignition in position "ON" and "START")
|-
|100||Data link (flash signal, pin 26 on diagnostic port, C-121)
|-
|}</text>
    <sha1>f4d2b8d988c984586a3b4edffcd7f4389f15f2d0</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>TephraMod</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>433</id>
    <parentid>403</parentid>
    <timestamp>2010-01-14T20:21:00Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>/* Background &amp; Overview */  Add link to harness description.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25628" xml:space="preserve">--under construction-- please edit/fix ANY mistakes you see below!!!

This page will list out the various MOD's included in the TephraMOD patch package:

We have tried as hard has possible to keep MOD's between different ROMID's as consistant as possible, and currently there are TWO streams - EVO's WITH the "Intercooler Spray System" and those WITHOUT:

== Background &amp; Overview ==
The Tephra Mods are developed by a great Australian with the forum nickname "Tephra".  The basis for these mods were a few simple modifications that had to be ported to a ROM by each individual user.  Around the time when map switching was coming around it was determined that it would be easier to distribute a ROM to use as an actual base, and allow the user to copy their specific maps and changes into the upgraded ROM.&lt;br&gt;
&lt;br&gt;
Thus the Tephra ROM was born.  This began at "version 5".  So far there have also been version 5.10, v6 (mostly testing for V7), and V7.  Each version adds new features and fixes others.  Mods by other modders are often made compatible with these roms because they offer such a good feature base.&lt;br&gt;
&lt;br&gt;
A [[map switching harness]] is not required to use the Tephra ROM, but is required if you desire to use the map switching feature and do not have an ICS switch.  It is possible to use a switching harness with an ICS, and also to build a custom harness using a master on/off from something like an Aquamist injection kit to control the map switching.  Harnesses are sold by Jack_of_Trades, but he also provides schematics to create your own.&lt;br&gt;
&lt;br&gt;
Please note that not all features may be available in your Tephra Rom Version.  Generally features are available in every version, but some may be dropped if they are deemed wasteful or unneeded.
&lt;br&gt;
&lt;br&gt;

== Versioning and changes ==
:* '''A note on ROM IDs:'''  
:** 96530006 is the universal Evo VIII Rom.  You should be able to use it on any VIII and some VIIs (if there is enough space on the flash memory).
:** 88580014 is the universal JDM/AUDM (twin solenoid).
:** 88590015 is the universal USDM/EDM IX rom.
:* '''Pro-Tip:'''  When upgrading between earlier versions (previous to V6) it is probably easiest to rename your current ECUFlash directory (IE: C:\Program Files\OpenECU\EcuFlash --&gt; C:\Program Files\OpenECU\EcuFlash1.35-v5.10 ) and start with a fresh install for the new Tephra-mod version.  This prevents frequent problems caused by xml overlap and helps to make sure you will not copy any incorrect information.  It also allows you to "step back in time" in case you ever need to look at an older ROM that you have.
=== [http://forums.evolutionm.net/ecuflash/313893-patch-knockcel-nlts-altmap-v4.html Version 4] **First Major Release ** ===
* NLTS:  no lift to shift
* 2 levels of knock CEL flash
* Map switching (timing/fuel/boost)
* Intercooler spray state restore - this remembers the last state you had it in.
* Intercooler spray linger - this just keeps spraying when you hit manual for your pre-defined period of time.
* Intercooler spray on knock - as per title, I usually keep it disabled because it uses too much water :P
* Alternate Map Support - gives you 4 additional maps (low_oct fuel+timing and high_oct fuel+timing)

=== [http://forums.evolutionm.net/ecuflash/332778-patch-tephramod-v5.html Version 5] **First Major Release ** ===
* Some basic ICS mods and fixes
* Rear o2 simulator (wave only, not heater)

=== [http://forums.evolutionm.net/ecuflash/362643-tephramod-v5-10-a.html Version 5.10] changes ===
(Note: version gap... some features may be rolled over from [http://forums.evolutionm.net/ecuflash/349239-tephramod-v5-8-testing-help-required.html V5.8] - it existed mostly as a testing release)
* added 2byte -&gt; 1byte load mod
* added MAP averaging
* fixed AutoICS AND Valet intermittent enablement after flash - the occurance of this should be MUCH less
* fixed valet mode lockout
* included 2byte load(removed in later versions), 2byte rpm, and 2byte airflow MUTS - just tick the box in evoscan
* 90550001 only - implemented the stationary rev limiter / Launch Control
* fixed NLTS load threshold bug (should lock load for NLTS at shift)
* fixed issue where altmap_by_adc0f wouldn't change to altmaps if toggle switch was already ON when car was first flashed

=== [http://forums.evolutionm.net/ecuflash/402800-tephramod-v6-testing.html Version 6] changes ===
(Note: these may be rolled into v7 as v6 was mostly a testing release)
* Added Versioning to ROM ID.  IE: 88590015 becomes 88590'''6'''15 (Makes XML changes MUCH easier)
* Cranking Enrichment addition to "altmaps"
* Boost Drop for High knock
* AFR safety CEL Flash
* AFR safety boost drop
* Airflow calcs (g/s etc)
* TPS+IAT corrections for WGDC maps
* 3d boost maps with gear/rpm axis's
* Removed alternate Low Octane Maps (defaults to primary low octane maps during octane interpolation)

=== [http://forums.evolutionm.net/ecuflash/451836-tephramod-v7.html Version 7] changes ===
* Launch Map mode
** uses TPS + SPEED to impose a different fuel+timing map
* Altmap toggle by TPS (like Valet, CANNOT be used with Valet)
* BIGMAPs added (30x25 Maps for Fuel &amp; Timing) - Do not use the original maps!
* Removed 2byte load AND 2byte RPM
* Added Speed Density and live map Versioning to ROM ID.  IE: 8859'''0'''015 becomes 8859'''2'''015 (Makes XML changes MUCH easier)
** 0 = MAF
** 1 = Speed Density
** 2 = DMA (Live Map) + MAF
** 3 = DMA (Live Map) + Speed Density
* Added MrFred Airflow Calcs for g/s or lb/min

= Main Tephra Mod Options Table =
=== Valet Mode ===
Allows you to enable a "Valet" mode thereby disabling some features to prevent unintended "hoonage" by valets, friends, theives, etc.  When enabled valet mode can be activated or deactivated by turning the key to the 'ON' position without starting the car and pressing the gas pedal for the time specified in the 'Valet Rev Limit Time to Activate' table of the Tephra Mods section.  The CEL will then flash for the amount of time specified in 'Valet Rev Limit Flash Time' table.  It will also flash when the car is started.  When enabled RPM will be limited to the value specified in the 'Valet Rev Limit' table ('''Note:''' if this is too low your car will not be able to idle properly and will shut off).  As of V7 WGDC should also be set to 0% while in valet mode. &lt;br&gt;
'''Enable Valet Mode'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Valet mode in the ROM:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Auto-Valet on Fresh Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Auto-Valet mode in the ROM.  This will enable valet mode each time the car is shut off unless you follow the proceadure to disable it:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
=== Other Options ===
Enable Alternate Maps Master ADC0F=1, AutoICS=2 &lt;br&gt;
'''Enable Alternate Maps Master ADC0F=1, AutoICS=2''' &lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for Alt Maps in the ROM:
::* 0 = Disabled
::* 1 = Enabled - Switched via Map switch into ADC0F pin of ECU
::* 2 = Enabled - Switched via ICS Switch
&lt;br&gt;
'''Restore ICS State Fresh Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable restoring the state of the ICS setting which would normally default to off every time the car was started:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Flash ICS when on Alternate Map'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable forcing the ICS light to flash when you are in alternate map mode:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Flash CEL on Knock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable Flashing the 'Check Engine' light when a knock value exceeds the value in the 'KnockSum Required for Slow CEL (Low Knock)' table in the Tephra Mods section.  If you exceed the value set in the 'KnockSum Required for Fast CEL (High Knock)' table the light will flash twice as fast.  You must exceed the value set in 'Load Required for CEL on Knock' for the flash to occur.  The light will flash for the time set in 'CEL on Knock Flash Time' (set in milliseconds):
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''+ Drop boost on High-Knock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to set WGDC to 0% if you exceed the value set in the 'KnockSum Required for Fast CEL (High Knock)' table.  The WGDC will remain at 0% for the amount of time specified in the 'High Knock Boost Drop Time' table:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Manual ICS Linger'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable... NEED MORE INFO:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Spray ICS on Kock'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to trigger the ICS on a set knock point (or any knock?):
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable No Lift to Shift'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for NLTS in the ROM:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Rear O2 Simulator'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to help prevent a CEL for users with a high flow catalytic converter.  It will simulate the rear O2 signal based off of the front O2 signal to help prevent catalytic efficiency check errors:
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable MAP Averaging'''&lt;br&gt;
: For users who have direct boost control this helps to stabilize the boost that is "seen" by the ECU via the JDM MAP (or whatever is on that channel).  Rather than reporting the most recent reading, the ECU will see a running average of the most recent 3 MAP values.  It is calculated as 
&lt;pre&gt;[n-2 sample average] + [n-1 sample] + [n sample]&lt;/pre&gt;
::* 0 = Disabled
::* 1 = Enabled
: Note:  Setting this will reflect the updated averaged value when logging the default MUT Item for boost.  A value can be set at another location to log *actual* boost.
&lt;br&gt;
'''Enable Manifold Temperature'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable MAT logging via temperature sensor input in the Manifold when disabling the fuel temperature sensor.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable WBO2 Check AFR Safety'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable a CEL Flash when AFR is out of range.  You must have an analog wideband signal wired into your rear O2 ADC input for this to function.  You must exceed the value in the AFR Safety Load Threshold table and then have the input voltage from the wideband out of the range set in the 'AFR Safety Min AFR' and 'AFR safety Max AFR' tables.  When enabled the CEL will flash for the amount of time specified in the 'AFR Safety Boost Drop Time and Flash Time' table.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''+ Drop Boost on AFR out of Range'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable a boost drop via 0% WGDC when the conditions for 'Enable WBO2 Check AFR Safety' are met.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable AirFlow Calcs'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable a the MrFred airflow calcs for g/s or lb/min.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;
'''Enable Launch Maps'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is used to enable launch maps while the TPS and speed conditions are met.
::* 0 = Disabled
::* 1 = Enabled
&lt;br&gt;&lt;br&gt;

= Detailed Options =
=== 1 Byte Load ===
'''AKA: 2byte to 1Byte Load Factor'''&lt;br&gt;
&lt;br&gt;
This is a mod to allow a high resolution load value to fit into a 1 byte loggable item.  Logging less items will increase the frequency at which you log other items.  The main reason this is a factor is that by default all loggable items are a bit-wise representation of a value, or a number from 0-255 pumped into an equation to represent another value.  What this means is that from the factory you must log [[2-Byte_Logging|2 bytes]] to show load greater than 255 since it is a 1:1 item as output to a datalogger.&lt;br&gt;
&lt;br&gt;
The TephraMod simply reduces this number by a factor of whatever you have it set to.  By default, this should be 1.2.  Thus, the maximum value for load with this setting is [255 * 1.2 = ] 306.  The ECU calculates [ load / 1.2 ] and sends this value to the logger.  The logger then takes [ load sent * 1.2 ] and shows you an accurate and efficient representation of load.
:* Your Evoscan/Mitsulogger calculation MUST match the number in your tephra rom for an accurate representation.
:* Obviously a higher number will allow for a higher maximum, but lowers your resolution slightly.
:* If you overrun the maximum value your load will [http://forums.evolutionm.net/7066566-post789.html "loop over"] in the log (see below or [http://forums.evolutionm.net/ecuflash/422054-these-1byte-load-spikes-normal.html Here]).
&lt;br&gt;
&lt;center&gt;[[Image:1byteload_spikes_sm.JPG]]&lt;/center&gt;
&lt;br&gt;

=== BIG MAPs ===
This is a mod to add resolution to the Main, Alternate, and Launch Fuel and Timing tables.  It adds resolution to the maps to allow for more discreet control over where fueling and timing changes take place.  In addition to this, it allows you to separate the representative axes on from other maps preventing problems that occur when not rescaling EGR maps or other unknown maps that may effect timing and fueling, but use the same defined axes as the original fuel and timing maps.  The resolution of the original maps is 18x15 (VIII Fuel) and 19x20 (VIII Timing) or 20x15 (IX Fuel) and 21x20 (IX Timing).  The Big maps are all 30x25 (Horizontal x Vertical).&lt;br&gt;
&lt;br&gt;
Maps included should be properly converted for stock values.  If you have modified your maps the [http://forums.evolutionm.net/7597112-post3.html Big Map Converter] will help to properly re-shape your maps to fit properly in the big-maps.&lt;br&gt;
&lt;br&gt;
* Note: Do NOT use or change your original fuel and timing maps.  They no longer do anything.
&lt;br&gt;

=== Launch MAPs ===
This is a mod to allow a different set of maps for launching.  It allows you to lower your fuel and timing during launch to allow for a higher boost build up without creating a hole in the normal map that you might drive through.  This is more conducive to allowing these changes on a fully driven car (street, road race, and strip) instead of a map that should only be used on the drag strip.&lt;br&gt;
&lt;br&gt;
Ideally the launch map should look just like your regular map, but have a modification for richer fuel and lower timing in the area of the RPM and load of your stationary rev limiter.  Note that too rich of AFR and especially too low of timing can cause knock on launch and negate the benefits of this patch.&lt;br&gt;
&lt;br&gt;
'''Launch-Map TPS Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before Launch maps will be switched:
::* Default: 40 Load
&lt;br&gt;
'''Launch-Map Speed Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before Launch maps will be switched:
::* Default: 8 km/h
&lt;br&gt;
&lt;br&gt;

== NLTS - No Lift to Shift ==
No Lift to Shift or NLTS allows the driver to keep the car at WOT whilst shifting - this has a number of advantages:&lt;br&gt;
* Boost that is built up isn't lost when the TPS is slammed shut and the BOV is activated&lt;br&gt;
* When done correctly a NLTS WOT Shift should do less damage to the driveline than a normal WOT Shift&lt;br&gt;
&lt;br&gt;
Tephra's implementation of NLTS is very simple, when the preset conditions (Load/TPS/Speed/Clutch Down) are met&lt;br&gt;
the ECU "remembers" what RPM you shifted at and imposes a temporary rev limiter at that RPM - the configurable "RPM Drop".&lt;br&gt;
&lt;br&gt;
eg - If your RPM Drop parameter is 1500 and you shift at 7500RPM, then a rev limiter (like the normal 7606 RPM rev&lt;br&gt;
limiter) will be imposed at 6000RPM, this means whilst you are shifting AND the RPM are higher than 6000RPM the&lt;br&gt;
engine is experiencing FUEL CUT.&lt;br&gt;
&lt;br&gt;
Once you get off the clutch pedal the normal rev limiter (7606RPM by default) is re-imposed.&lt;br&gt;
&lt;br&gt;
=== Problems with NLTS ===
Because we are using the TOP CLUTCH SWITCH some people find they are enabling NLTS by accident as the clutch&lt;br&gt;
pedal doesn't need to travel very far to de-activate this switch. ALSO Make sure you fully come of the clutch pedal&lt;br&gt;
otherwise the rev limiter will still be imposed.&lt;br&gt;
Alternatively you can put some foam on the clutch pedal (where the switch contacts) to lengthen the travel of the clutch&lt;br&gt;
pedal allowed before switch de-activates.

[[Image:Nlts-settings.png]]
=== NLTS Settings ===
'''Enable No Lift to Shift'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, it is a global enable/disable setting for NLTS in the ROM:
::* 0 = Disabled
::* 1 = Enabled
: In the above image it is set to 0, thus NLTS is disabled and the other NLTS settings are irrelevant.&lt;br&gt;&lt;br&gt;
'''NLTS TPS Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0% to 100%
: In the above image it is set to 98%, meaning once all the other conditions are met NLTS will impose the rev limiter once the TPS is over 98%.  Some users recommend something lower like 80%.&lt;br&gt;&lt;br&gt;
'''NLTS Load Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0% to 400%
: In the above image it is set to 150%, meaning once all the other conditions are met NLTS will impose the rev limiter once the Load exceeds 150%.  Some users recommend something lower like 100, but you don't want to prevent free revving for down shifting.&lt;br&gt;
: (NOTE: This condition isn't used for disabling the rev limiter because Load drops when the NLTS rev limiter is engaged)&lt;br&gt;&lt;br&gt;
'''NLTS Speed Threshold:'''&lt;br&gt;
: This setting is found in the "Mods" group - essentially it is one of the conditions that must be met before NLTS will impose the rev limiter:
::* 0km/h to 250km/h
: In the above image it is set to 30km/h, meaning once all the other conditions are met NLTS will impose the rev limiter once the Speed exceeds 30km/h&lt;br&gt;
: (NOTE: This condition allows the driver to slip the clutch on launch, without it you may hit NLTS on launch which would be bad)&lt;br&gt;&lt;br&gt;
'''NLTS RPM Drop:'''&lt;br&gt;
: This setting is found in the "Mods" group - Essentially it tells the ECU what at RPM to impose the rev limiter:
::* 0rpm to 3000rpm
: In the above image it is set to 800rpm, meaning once all the conditions are met NLTS will impose the rev limiter at the CURRENT RPM - RPM Drop&lt;br&gt;
: ie if you shift at 6500RPM then the rev limiter would be set to 5700RPM&lt;br&gt;&lt;br&gt;

== Intercooler Spray (ICS) Mods ==


[[Image:Ics-settings.PNG]]

=== ICS Settings ===
'''Restore ICS State on Ignition'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, when enabled the ICS system state (little green lamp) will be restored:
::* 0 = Disabled - ie don't restore the ICS Auto State on Fresh Ignition
::* 1 = Enabled - ie restore the ICS Auto State on Fresh Ignition
: In the above image it is set to 1, thus when the car is first turned on it will restore the same state that the car was in before it was turned off last.&lt;br&gt;&lt;br&gt;
'''Enable Manual ICS Linger:'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table, on a stock Evo pressing the Manual ICS button will spray for the duration of the press, this modification causes the spray to keep going for as long as you have configured.
::* 0 = Disabled - ie don't cause the manual ICS button to keep spraying
::* 1 = Enabled - ie cause the manual ICS button to keep spraying
&lt;br&gt;
'''Manual ICS Linger Time'''&lt;br&gt;
: This setting is found in the "Mods" group, it specifies how long to spray after the Manual button has been released:
::* 0ms to 5000ms 
: In the above image it is set to 1500ms, thus when the manual ICS button is pressed and released the ICS will spray for 1.5 seconds longer.&lt;br&gt;&lt;br&gt;
'''Enable Spray ICS on Knock:'''&lt;br&gt;
: This setting is found in the "Tephra Mod Options" table
::* 0 = Disabled - ie default evo behaviour
::* 1 = Enabled - ie when enabled (and on AutoICS) this will cause the ICS system to spray once the other conditions have been met.
&lt;br&gt;

== Boost Control ==
With Standard Tephra Mod the WGDC 2 &amp; 3 tables are removed.  Curious eyes will notice that WGDC 2 actually becomes the boost control table for alt-maps.
&lt;br&gt;
&lt;br&gt;
''' WGDC=100% under this Load '''
Sets a load value up until which your WGDC will be 100%.  Setting this too high can result in spikes on spoolup.  Setting it too low can result in slower spool.  Better to have it too low than too high.
:* You must still meet the min required load for boost control condition for this to switch WGDC to 100%
:* Note: Setting too high can cause a strange feeling at the threshold in 5th and 6th gear where loads are higher at lower boost pressures (as of v6).  This may be corrected in later versions.

&lt;center&gt;Typical result of WGDC 100% under this load feature &lt;br&gt; [[Image:20090528WGDC_100p_under_load.JPG]]&lt;/center&gt;
&lt;br&gt;
&lt;br&gt;

''' MAF IAT WGDC Correction '''
This is used to reduce/increase wgdc based on IAT.  This helps to prevent boost overshoot in cold weather (or undershoot in hot weather, if you prefer).  Setting a negative value of x will reduce your base wastegate duty cycle (in percentage) by that amount.
&lt;br&gt;
&lt;br&gt;

''' TPS WGDC Correction '''
Used as a multiplier to reduce base WGDC relative to TPS.
&lt;br&gt;


=== Gear Based Boost Control ===
''' RPM/Speed to Gear ''' &lt;br&gt;
This table loosely defines something similar to the gear ratios for your car so that gear can be accurately determined.  The calculations in the table simply divide RPM by speed (since actual speed is calculated at the transmission and not the tire) to do so.
&lt;br&gt;
The best way to determine correct values for this table is to log while driving (added in v6) and take an average of the numbers while in each gear over a good portion of the RPM range.  Do not include numbers reported while the clutch is disengaged or "settling".
:* The numbers do not have to (and cannot) be exact.  The system will 'snap' to the closest value it can.
:* The ratio for gear 5 and 6 may be similar.  If you have a 6 speed you *may* want to use a value 1 higher for gear 5 or 1 lower for gear 6.
:* If you have a 5 speed set the value for gear 6 to something like '1' where it will never be reached.  Otherwise you will have to make any gear based tables the same for gears 5 and 6.
:* Gear 0 represents Neutral.
:* 'RPM/Speed Ratio Filter Strength' should not need to be adjusted.  It is hidden in later XML versions.
&lt;br&gt;

''' Baseline Boost &amp; Alternate Baseline Boost ''' &lt;br&gt;
These tables now represent your boost control tables.  It was found the stock ECU had 2 levels of boost control, but it was disabled from the factory.  Tephra decided to make things even better.  As with the gear defining RPM/Speed Ratio table gear 0 represents Neutral.
:* Your normal boost control tables are no longer needed.  You can ignore them or remove them from your XML.
:* Direct boost control mods are applied in exactly the same way for these tables as they are for the normal tables.  After you have applied the patch just change the scaling of the table to see a proper representation.
&lt;br&gt;

==Alt Maps==
integrated with Aquamist HFS-1, GM BCS, and direct boost control mod [http://forums.evolutionm.net/showthread.php?t=334575 here] and [http://www.youtube.com/watch?v=dWUNj-s3GBE video here]

====Checking Switch Functionality and Logging Alt Map status====
To log and verify that your alt-map switch is functioning properly make a copy of your map and change [[Add_MUT_Table_To_EcuFlash|MUT]] values to log 0x6B0D (Voltage in bits) and 0x8425 (altmaps: 0-normal, 3-alt (4-alt in 88590015)).

For example, you can temporarily set:
{|border="1" cellpadding="5" cellspacing="0"
|MUT00:
|0x8425
|-
|MUT83:
|0x6B0D
|}
&lt;br&gt;
Then, to log in [[EvoScan]] add these definitions:
{|border="1" cellspacing="0"
|&lt;nowiki&gt;&lt;DataListItem DataLog="N" Color="" Display="ALT MAP Activation" LogReference="AltMapActive" RequestID="00" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="5" ChartMin="0" ChartMax="5" ScalingFactor="1" Notes="Alt Map Activation. 0= Standard Maps 3= Alt Maps" Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;&lt;DataListItem DataLog="N" Color="" Display="ALT Map Input Voltage" LogReference="AltMapVoltage" RequestID="83" Eval="x*5/255" Unit="Vdc" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="5" GaugeMax="15" ChartMin="0" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|}
&lt;br&gt;
Or MitsuLogger with these defs:
{|border="1" cellspacing="0"
|&lt;nowiki&gt;&lt;Request LogReference="AltMapActive" RequestID="00" Eval="x" Unit="unit" Logged="y" Response="1"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;&lt;Request LogReference="AltMapVoltage" RequestID="83" Eval="x*5/255" Unit="Vdc" Logged="y" Response="1"/&gt;&lt;/nowiki&gt;
|}
&lt;br&gt;
After you see that your switch is working properly, your voltage is &lt;5V (Ideally it should be &lt;4.7V), and your alt-maps are being activated you should switch back to the map without the modified MUT00.  You can also remove the info from your [[Evoscan]]/Mitsulogger XML.</text>
    <sha1>b0b558b302f00f75e00fc271110fcdeaf1231649</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Map switching harness</title>
  <ns>0</ns>
  <id>248</id>
  <revision>
    <id>935</id>
    <parentid>934</parentid>
    <timestamp>2010-01-14T20:21:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8268" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested; however, details on building your own [[map switching harness]] are available here as well.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for position #42 on the ECU harness.
:: Evo IX: '''small''' pin, for position #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Pin removal ==

Thanks to mrfred for this [http://forums.evolutionm.net/5191835-post379.html fantastic writeup] on the process of removing pins from the IX harness. Essentially, pull back the retaining clip ("secondary restraint), and the pins should come out easily with a tug.

See these two posts ([http://forums.evolutionm.net/5107038-post122.html 1] and [http://forums.evolutionm.net/5107038-post123.html 2]) from Richard L. (Aquamist) for an example of how to unlock the pins on a VIII harness. Basically, lift the white strip from the plug approximately 1/16" with a very small, flat-tipped screwdriver, and the pin you want to remove should pop right out.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>fcc2b6e0baa7ffbe9b1c3961d12433c320dd4cab</sha1>
  </revision>
  <revision>
    <id>934</id>
    <parentid>933</parentid>
    <timestamp>2010-01-14T20:23:05Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Undo revision 874 by [[Special:Contributions/EdwardMarshall|EdwardMarshall]] ([[User talk:EdwardMarshall|Talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8176" xml:space="preserve">One of the additions you get with [[TephraMod]] is map switching: alternating between a primary and secondary set of fuel, timing, and boost maps depending on the position of a switch. Originally, development of this feature happened in a [http://forums.evolutionm.net/ecuflash/314505-meth-failsafe-patches.html thread on EvoM]; at this point, the feature is considered mature.

Much of the information in this page came from [http://www.dsm-ezine.com/evoVIII_adc_switch.html Jack_of_Trades' map switching webpage]; unfortunately, details on assembling your own switching harness are no longer available there, in lieu of links to several vendors who will sell pre-made harnesses. For many users, it may be easier to simply buy one that has been professionally assembled and tested.

= Parts List =

: 1 x ECU pin; see [[Plugs, Pins, and Connectors]] for part numbers:
:: Evo VIII: '''large''' pin, for position #42 on the ECU harness.
:: Evo IX: '''small''' pin, for position #64 on the ECU harness.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062497&amp;cp SPST (single pole, single throw) ON/OFF Switch]
:: It can be any SPST switch but it cannot be one with a built-in light because the switch will only have 5VDC flowing through it and only 0.05 mA of current, not enough to power any light or LED.

: 25 ft. roll x [http://www.radioshack.com/product/index.jsp?productId=2062648&amp;cp=&amp;pg=1&amp;searchSort=TRUE&amp;sr=1&amp;retainProdsInSession=1&amp;y=7&amp;origkw=speaker+wire&amp;kw=speaker+wire&amp;x=23&amp;s=A-StorePrice-RSK&amp;parentPage=search 18 Gauge 2-Conductor Speaker Wire]
:: You only need enough wire to go from the ECU harness (located under the passengers side dash) to the location you desire to install your on/off switch and also to the location you choose to mount the LED indicator light.  I suggest running 5 feet for the switch, 5 feet for the L.E.D. and two feet to go from the resistors to the ECU harness for a total of roughly 10 to 12 feet of speaker wire.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062343&amp;cp=&amp;sr=1&amp;origkw=1k+ohm+resistor&amp;kw=1k+ohm+resistor&amp;parentPage=search 1K Ohm 1/4 Watt Resistor]
:: This will be installed between the +12Vdc source and the ADC input on the ECU.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2994587&amp;cp=&amp;sr=1&amp;origkw=10k+ohm+resistor&amp;kw=10k+ohm+resistor&amp;parentPage=search 10K ohm 1/8 Watt Resistor]
:: This will be installed in conjunction with the 4.7V zener diode.  This will help to eliminate any noise in the signal going into the ECU when the switch is in the "OFF" position.

: 1 x 4.7 volt 1-watt Zener Diode
:: This will be installed between the 1K ohm resistor and the ECU pin and limits the input voltage to only 4.4-5.0 volts (for +/- 5% tolerance versions). Be sure the black stripe is oriented in the same direction as the diagram. You never want to exceed 5.0 volts to the ADC input into the ECU. Search online for this part.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062321&amp;cp 560 ohm 1/2 Watt Resistor]
:: This will be installed between the +12Vdc source and the 1.8Vdc LED indicator light.  It will lower the voltage to a safer 1.8Vdc for the LED to operate properly.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2103802&amp;cp=&amp;sr=1&amp;origkw=5mm+led&amp;kw=5mm+led&amp;parentPage=search 5mm 1.8Vdc LED]
:: The LED isn't absolutely necessary on Evo's equipped with an ICS system because you can use the ICS light in the instrument cluster as your indicator. This option is up to the user. I personally prefer the L.E.D. so I don't have to see the ICS light blinking.

: 1 x [http://www.radioshack.com/product/index.jsp?productId=2062558&amp;cp=&amp;sr=1&amp;origkw=led+holder&amp;kw=led+holder&amp;parentPage=search 5mm LED Holder]
:: This holds the LED into the panel where you choose to mount it.  Just drill a 1/4" hole and it snaps in.  A good tip is to place a dab of super glue on the backside of the panel to keep the holder from popping out. It is an Evo after all and they don't have the smoothest suspension.

: [http://www.radioshack.com/product/index.jsp?productId=2104090&amp;cp=&amp;sr=1&amp;origkw=heat+shrink&amp;kw=heat+shrink&amp;parentPage=search Assorted packet of Heat Shrink Tubing]
:: This will protect all of your electrical connections. Simply slide it over the wire and heat the tubing with a cigarette lighter or butane torch.

= Wiring diagrams =

== Evo VIII ==

[[Image:ADC-evo8-harness.jpg]]

== Evo IX ==

[[Image:ADC-evo9-harness.png]]

= Instructions =

== Crimping the pin ==

To crimp the ECU pin onto your wire, strip back approximately 1/8" of insulation, and place the wire in the pin such that the insulation is under the outside tabs, but the bare wire is under the inside tabs. Fold one rear tab over the insulation snugly, then fold the other over on top of it, taking care not to "squish" the pin; if you crush the pin so that it is too wide, it may not fit inside the ECU harness plug. Repeat the folding procedure with the inside tabs, and consider adding a drop of solder to ensure a good, secure connection.

== Pin removal ==

Thanks to mrfred for this [http://forums.evolutionm.net/5191835-post379.html fantastic writeup] on the process of removing pins from the IX harness. Essentially, pull back the retaining clip ("secondary restraint), and the pins should come out easily with a tug.

See these two posts ([http://forums.evolutionm.net/5107038-post122.html 1] and [http://forums.evolutionm.net/5107038-post123.html 2]) from Richard L. (Aquamist) for an example of how to unlock the pins on a VIII harness. Basically, lift the white strip from the plug approximately 1/16" with a very small, flat-tipped screwdriver, and the pin you want to remove should pop right out.

== Mounting Suggestions ==

Once you have made your harness, you need to decide on where to install the LED indicator and the on/off switch.   Be sure to give yourself enough wire to reach just about any location in the nearby vicinity of the drivers seat in case you decide to install either in a different location than you originally intended.

Here are the two locations I used and they are very discrete and easy to access while driving.

* I decided to mount the on/off switch inside the map pocket below the radio bezel. It is easily removable and only secured with the two mounting screws visible in the photo to the right.  I chose this location on the panel because it was well within reach from the drivers seat and there wasn't any interference behind the panel where the body of the switch would get tucked away.  Be sure to check your clearances behind any panel you decide to mount the switch.  All that is required is a 1/4" drilled hole.

* I mounted the LED on the same panel because of its ease of removal and it isn't in the DIRECT line of sight.  You don't want this LED blazing in your eye constantly while driving.  This location points the LED slightly downward while still doing a GREAT job of visually showing you when the ALT MAPS are activated.  I chose a 120mcd brightness LED after trying 10 different brightness LEDs and this is the least over-bearing at night while still being completely visible during a bright day.   To install, just drill a 1/4" hole and insert the LED Holder from the front of the panel.  Snap the LED in from the backside into the LED holder and you're done.

''Tip:'' To ensure the LED holder will stay firmly flush with the panel, apply a drop of super glue to the backside of the panel where it makes contact with the side of the LED holder.  Don't glue your hands together kids.

== Videos ==

These videos were originally put together by Jack_of_Trades, and are hosted on his website.

=== Accessing the ECU harness ===

http://dsm-ezine.com/EVO_ADC/accessing_ecu_harness_evo.wmv

=== Installing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/installing_ecu_pin_evo.wmv

=== Removing an ECU pin ===

http://dsm-ezine.com/EVO_ADC/remove_ecu_pin_evo.wmv

=== Connecting to power and ground ===

http://dsm-ezine.com/EVO_ADC/tapping_onto_existing_ecu_wire.wmv

=== Evo Map Switching: ADC and ICS ===

http://dsm-ezine.com/EVO_ADC/adc_map_switching_evo.wmv

http://dsm-ezine.com/EVO_ADC/ics_map_switching_evo.wmv</text>
    <sha1>a9227b41b15bba45452e4f96ab0c69b10d6c6d4e</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:Openport.pdf</title>
  <ns>6</ns>
  <id>250</id>
  <revision>
    <id>940</id>
    <timestamp>2010-01-25T19:19:23Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>OpenPort original design.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">OpenPort original design.</text>
    <sha1>1cb7c38831a90fead5c3bbc06e22e452df329e08</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:Openport12.pdf</title>
  <ns>6</ns>
  <id>251</id>
  <revision>
    <id>941</id>
    <timestamp>2010-01-25T19:19:45Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>OpenPort schematic, version 1.2.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">OpenPort schematic, version 1.2.</text>
    <sha1>9fd5f5c6726e789e4e9d4e7fb4b14ff50e6ee27b</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>ECU Development</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>656</id>
    <parentid>647</parentid>
    <timestamp>2010-01-25T19:22:43Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="787" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>694958460bc92286a13262252e97160d0cbd49e6</sha1>
  </revision>
  <revision>
    <id>657</id>
    <parentid>647</parentid>
    <timestamp>2010-02-05T22:47:43Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="824" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>69c361d97fab6d5ef8176d1cd238436ad975af38</sha1>
  </revision>
  <revision>
    <id>647</id>
    <timestamp>2010-05-03T15:26:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1170" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf  schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>4559076ad5687f7d573a56926f7b7a53c8faa4b2</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>OBD Pinout</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>850</id>
    <timestamp>2010-01-25T22:52:47Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="735" xml:space="preserve">OBD Mitsu pinout (from [http://forums.evolutionm.net/7694918-post7.html a post acamus made]):

[[Image:OBD-connector-pinout.png]]

{| border=1 cellspacing=0 cellpadding=5
| 1||Diagnosis control line 
|-
| 2||J1850 (+) line
|-
| 3||Suspension - ECS - 
|-
| 4||Chassis ground
|-
| 5||Signal ground
|-
| 6||Transmission - ELC-4/5AT
(CAN high; ISO 15765-4 and SAE-J2284)
|-
| 7||К-Line (ISO 9141-2, ISO 14230-4) - ECU, ABS, SRS
|-
| 8||Brake – ABS
|-
| 9||ETACS: Pulse signal only 
|-
|10||J1850 (-) line
|-
|11||Air Conditioner - Full Auto AC
|-
|12||Air Bag – SRS 
|-
|13||Cruise Control – ASC 
|-
|14||Vehicle speed signal
(CAN low; ISO 15765-4 and SAE-J2284)
|-
|15||L-line (ISO 9141-2, ISO 14230-4)
|-
|16||Power supply +12V
|}</text>
    <sha1>376d2cdaacaea00fe1fed67e0e03577e999bfc12</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>MUT Requests</title>
  <ns>0</ns>
  <id>218</id>
  <revision>
    <id>814</id>
    <parentid>808</parentid>
    <timestamp>2010-01-26T13:44:17Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>More acamus additions.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8703" xml:space="preserve">The following table attempts to collect the requests that are query-able via the MUT-III protocol on ''stock'' vehicles. Not all entries will apply to all Mitsubishi vehicles. Formulas are expressed in a format compatible with [[EvoScan]].

'''Please Note:'''
*"Calculated" formulas (sometimes referred to as "math channels") are intentionally not listed here, nor are common modifications to the MUT table.
* As we understand it, MUTs are [http://forums.evolutionm.net/7093180-post821.html only used for logging purposes.]  Changing a MUT value should have no effect on internal ECU calculations.
* Many of these were dreived from Acamus' list [http://forums.evolutionm.net/ecuflash/421565-found-new-items-log.html#post7075360 here].

Only request IDs 00 through BF are valid MUT requests. IDs higher than BF are actually [[MUT Commands]], which control actuators for various functions driven by the ECU: solenoids, pumps, etc.


&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!ID2
!Short Name
!Description
!Units
!Formula
!Comment
|-
|04
|
|TimingAdv
|Timing Advance Interpolated
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance Scaled
|degrees
|x-20
|
|-
|06
|
|TimingAdv
|Timing Advance
|degrees
|x-20
|
|-
|07
|
|CoolantTemp
|Coolant Temp
|F
|x*1.8+32
|
|-
|0C
|
|LTFTLo
|Fuel Trim Low (LTFT)
|%
|[http://forums.evolutionm.net/7033482-post29.html (x-128)/5]
|
|-
|0D
|
|LTFTMid
|Fuel Trim Mid (LTFT)
|%
|(x-128)/5
|
|-
|0E
|
|LTFTHigh
|Fuel Trim High (LTFT)
|%
|(x-128)/5
|
|-
|0F
|
|STFT
|Oxygen Feedback Trim (STFT)
|%
|(x-128)/5
|
|-
|10
|
|CoolantTempScaled
|Coolant Temp Scaled
|F
|1.8*x-40
|
|-
|11
|
|MAFAirTempScaled
|MAF Air Temp Scaled
|F
|1.8*x-40
|
|-
|12
|
|EGRTemp
|EGR Temperature
|F
| -2.7*x + 597.7
|
|-
|13
|
|O2Sensor
|Front Oxygen Sensor
|V
|0.01952*x
|
|-
|14
|
|Battery
|Battery Level
|V
|0.07333*x
|
|-
|15
|
|Baro
|Barometer
|kPa
|0.49*x
|
|-
|16
|
|ISCSteps
|ISC Steps
|steps
|x
|
|-
|17
|
|TPS
|Throttle Position
|%
|x*100/255
|
|-
|18
|
|
|Open Loop Bit Array
|
|
|
|-
|19
|
|
|Startup Check Bits
|
|
|
|-
|1A
|
|AirFlow
|Air Flow - (TPS Idle Adder ?)
|Hz
|6.25*x
|
|-
|1A
|
|
|TPS Idle Adder
|
|
|
|-
|1C
|
|Load
|ECULoad
|load
|5*x/8
|
|-
|1D
|
|AccelEnrich
|Acceleration Enrichment - (Manifold_Absolute_Pressure_Mean ?)
|airflow/rev
|200*x/255
|
|-
|1F
|
|PrevLoad
|ECU Load Previous
|load
|5*x/8
|
|-
|20
|
|RPM_Idle_Scaled
|Engine RPM Idle Scaled
|RPM
|31.25*x
|
|-
|21
|
|RPM
|Engine RPM
|RPM
|31.25*x
|
|-
|24
|
|TargetIdleRPM
|Target Idle RPM
|RPM
|7.8*x
|
|-
|25
|
|ISCV_Value
|Idle Stepper Value
|count
|x
|
|-
|26
|
|KnockSum
|Knock Sum
|count
|x
|
|-
|27
|
|OctaneFlag
|Octane Level
|%
|100*x/255
|
|-
|29
|2A
|InjPulseWidth
|Injector Pulse Width
|ms
|x/1000
|
|-
|2C
|
|AirVol
|Air Volume
|
|x
|
|-
|2D
|
|
|Ignition Battery Trim
|
|
|
|-
|2E
|
|
|Vehicle speed Frequency
|Hz
|
|
|-
|2F
|
|Speed
|Speed
|MPH
|1.2427424*x
|
|-
|30
|
|Knock
|Knock Voltage
|V
|0.0195*x
|
|-
|31
|
|VE
|Volumetric Efficiency
|V
|0.0195*x
|
|-
|32
|
|AFRMAP
|Air/Fuel Ratio (Map reference)
|AFR
|(14.7*128)/x
|
|-
|33
|
|Corr_TimingAdv
|Corrected Timing Advance
|degrees
|x-20
|
|-
|34
|
|
|MAP Index
|
|
|
|-
|35
|
|
|Limp Home Fuel TPS Based
|
|
|
|-
|36
|
|
|Active Fault Count
|Count
|
|
|-
|37
|
|Stored Fault Count
|Count
|
|
|-
|38
|
|MAP
|Boost (MDP)
|PSI
|0.19348*x
|
|-
|39
|
|
|Fuel Tank Pressure
|PSI
|
|
|-
|3A
|
|UnscaledAirTemp
|Unscaled Air Temperature
|F
|x*1.8+32
|
|-
|3B
|
|
|Masked Map Index
|
|
|
|-
|3C
|
|O2Sensor2
|Rear Oxygen Sensor #1
|V
|0.01952*x
|
|-
|3D
|
|
|Front Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3E
|
|
|Rear Oxygen Sensor #2
|V
|0.01952*x
|
|-
|3F
|
|
|Short Term Fuel Feedback Trim O2 Map Index
|
|
|
|-
|40
|
|
|Stored Faults Lo
|
|
|
|-
|41
|
|
|Stored Faults Hi
|
|
|
|-
|42
|
|
|Stored Faults Lo 1
|
|
|
|-
|43
|
|
|Stored Faults Hi 1
|
|
|
|-
|44
|
|
|Stored Faults Lo 2
|
|
|
|-
|45
|
|
|Stored Faults Hi 2
|
|
|
|-
|47
|
|
|Active Faults Lo
|
|
|
|-
|48
|
|
|Active Faults Hi
|
|
|
|-
|49
|
|ACRelaySw
|Air Conditioning Relay
|On/Off
|x bit 4
|
|-
|4A
|
|PurgeDuty
|Purge Solenoid Duty Cycle
|%
|x*100/255
|
|-
|4C
|
|
|Fuel Trim Low Bank 2
|
|
|
|-
|4D
|
|
|Fuel Trim Mid Bank 2
|
|
|
|-
|4E
|
|
|Fuel Trim High Bank 2
|
|
|
|-
|4F
|
|
|Oxygen Feedback Trim Bank 2
|
|
|
|-
|50
|
|
|Long Fuel Trim Bank 1
|
|
|
|-
|51
|
|
|Long Fuel Trim Bank 2
|
|
|
|-
|52
|
|
|Rear Long Fuel Trim Bank 1
|
|
|
|-
|53
|
|
|Rear Long Fuel Trim Bank 2
|
|
|
|-
|54
|
|AccelEnrichTPS
|Acceleration Enrichment (increasing TPS)
|%
|x*100/255
|
|-
|55
|
|DecelLeanTPS
|Deceleration Enleanment (decreasing TPS)
|%
|x*100/255
|
|-
|56
|
|AccelLoadChg
|Acceleration Load Change
|%
|x*100/255
|Slope,Gradient,Derivative of load vs time.
|-
|57
|
|DecelLoadChg
|Deceleration Load Change
|%
|x*100/255
|Slope,Gradient,Derivative of load vs time.
|-
|58
|
|
|AFR Ct Adder
|
|
|
|-
|5B
|
|
|Rear O2 Voltage
|
|
|
|-
|5C
|
|
|ADC Rear O2 Voltage
|
|
|
|-
|60
|
|
|Rear O2 Trim - Low
|
|
|
|-
|61
|
|
|Rear O2 Trim - Mid
|
|
|
|-
|62
|
|
|Rear O2 Trim - High
|
|
|
|-
|63
|
|
|Rear O2 Feedback Trim
|
|
|
|-
|6A
|
|knock_adc
|knock adc processed
|count
|x
|
|-
|6B
|
|knock_base
|knock base
|count
|x
|
|-
|6C
|
|knock_var
|knock var (AKA Knock Sum Addition)
|count
|x
|
|-
|6D
|
|knock_change
|knock change
|count
|x
|
|-
|6E
|
|knock_dynamics
|knock dynamics
|count
|x
|
|-
|6F
|
|knock_flag
|knock flag (AKA Knock Acceleration)
|count
|x
|
|-
|70
|
|
|Array of Serial Receive Data Register 2 RDR 2 Values
|
|
|
|-
|71
|
|
|Sensor Error
|
|
|
|-
|72
|
|
|Knock Present
|
|
|
|-
|73
|
|
|Throttle Position Delta 1
|
|
|
|-
|74
|
|
|Throttle Position Delta 2
|
|
|
|-
|76
|
|ISCV % Demand
|[http://forums.evolutionm.net/7085804-post8.html ISCV % Demand (Columns)]
|%
|100*x/255
|
|-
|79
|
|InjectorLatency
|Injector Latency
|ms
|x
|
|-
|7A
|
|
|Continuous Monitor Completion Status 1
|
|
|
|-
|7B
|
|
|Continuous Monitor Completion Status 2
|
|
|
|-
|7C
|
|
|Continuous Monitor Completion Status 3
|
|
|
|-
|7D
|
|
|Non Continuous Monitor Completion Status OBD
|
|
|
|-
|7E
|
|
|Continuous Monitor Completion Status Low 4
|
|
|
|-
|7F
|
|
|Continuous Monitor Completion Status High 4
|
|
|
|-
|80
|81
|
|ECU ID Type
|
|
|
|-
|82
|
|
|ECU ID Version
|
|
|
|-
|83
|
|
|ADC Channel F
|
|
|
|-
|84
|
|ThermoFanDuty
|Thermo Fan Dutycycle
|%
|???
|
|-
|85
|
|EgrDuty
|EGR Dutycycle
|%
|????
|
|-
|86
|
|WGDC
|Wastegate Duty Cycle
|%
|x/2
|
|-
|87
|
|FuelTemperature
|Fuel Temperature
|F
|????
|
|-
|88
|
|FuelLevel
|Fuel Level
|???
|???
|
|-
|89
|
|
|ADC Channel 8 2
|
|
|
|-
|8A
|
|LoadError
|Load Error - (Throttle Position Corrected ?)
|load
|0.15625*x-20
|
|-
|8B
|
|WGDCCorr
|WGDC Correction
|%
|0.5*x-64
|
|-
|8E
|
|
|Solenoid Duty
|%
|
|
|-
|90
|
|
|Timer Status Register 9 TSR9
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled
|
|
|
|-
|9
|
|
|Timer Status Register 9 TSR9 Scaled Checked
|
|
|
|-
|9
|
|
|Fadout Timer Value
|
|
|
|-
|96
|
|MAF_ADC
|RAW MAF ADC value 
|
|
|
|-
|9A
|
|ACClutch
|AC clutch
|On/Off
|x bit 1
|
|-
|9B
|
|
|Output Pins
|
|
|
|-
|A2
|
|CrankPulse
|Crankshaft sensor pulse
|On/Off
|x bit 1
|
|-
|A2
|
|MafPulse
|MAF sensor pulse
|On/Off
|x bit 2
|
|-
|A2
|
|CamPulse
|Camshaft sensor pulse
|On/Off
|x bit 4
|
|-
|A8
|
|ATInShaftPulse
|Input shaft speed pulse (A/T)
|On/Off
|x bit 1
|
|-
|A8
|
|ATOutShaftPulse
|Output shaft speed pulse (A/T)
|On/Off
|x bit 2
|
|-
|A8
|
|ATGearL
|Gear: Low (A/T)
|On/Off
|x bit 32
|
|-
|A8
|
|ATGear2
|Gear: 2 (A/T)
|On/Off
|x bit 64
|
|-
|A8
|
|ATGear3
|Gear: 3 (A/T)
|On/Off
|x bit 128
|
|-
|A9
|
|O2HeaterFrontLeft
|Front O2 heater bank 1 (left)
|On/Off
|x bit 16
|
|-
|A9
|
|O2HeaterRearLeft
|Rear O2 heater bank 1 (left)
|On/Off
|x bit 32
|
|-
|A9
|
|O2HeaterFrontRight
|Front O2 heater bank 2 (right)
|On/Off
|x bit 64
|
|-
|A9
|
|O2HeaterRearRight
|Rear O2 heater bank 2 (right)
|On/Off
|x bit 128
|
|-
|AA
|
|Braking
|Brakes Pressed
|On/Off
|x bit 16
|
|-
|B3
|
|ATGearNeutral
|Gear: Neutral (A/T)
|On/Off
|x bit 1
|
|-
|B3
|
|ATGearDrive
|Gear: Drive (A/T)
|On/Off
|x bit 2
|
|-
|B4
|
|ATGearPark
|Gear: Park (A/T)
|On/Off
|x bit 64
|
|-
|B4
|
|ATGearRev
|Gear: Reverse (A/T)
|On/Off
|x bit 128
|
|-
|B7
|
|O2HeaterBrokenFrRt
|front O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|B8
|
|O2HeaterBrokenFrLt
|front O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|-
|B8
|
|NewACSwitch
|Air Conditioning Switch (Mattjin)
|Off/On
|x bit 1
|
|-
|B8
|
|PowerSteering
|Power Steering
|On/Off
|x bit 4
|
|-
|B9
|
|O2HeaterBrokenRearRt
|rear O2 heater circuit open (broken): bank 2 (right)
|Off/On
|x bit 8
|
|-
|BA
|
|O2HeaterBrokenRearLt
|rear O2 heater circuit open (broken): bank 1 (left)
|Off/On
|x bit 8
|
|}
&lt;/center&gt;</text>
    <sha1>a0e436e60c482b57bee757c43ba9a114c8aabd2e</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:1g aldl schematic simple.jpg</title>
  <ns>6</ns>
  <id>254</id>
  <revision>
    <id>949</id>
    <timestamp>2010-02-05T22:42:33Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Simple cable schematic for a 1g DSM ALDL datalogging cable.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="59" xml:space="preserve">Simple cable schematic for a 1g DSM ALDL datalogging cable.</text>
    <sha1>74e97ac683604e6d3ed581ad0edb6a4fa672fa21</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:1g aldl schematic complete.jpg</title>
  <ns>6</ns>
  <id>255</id>
  <revision>
    <id>950</id>
    <timestamp>2010-02-05T22:42:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>More complete cable schematic for a 1g DSM ALDL datalogging cable.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="66" xml:space="preserve">More complete cable schematic for a 1g DSM ALDL datalogging cable.</text>
    <sha1>b7b8d1618707e05a080475b8341a980c40be6616</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>1G DSM Datalogging Cable</title>
  <ns>0</ns>
  <id>256</id>
  <revision>
    <id>951</id>
    <timestamp>2010-02-05T22:47:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'For some applications, this passive schematic is enough:  [[Image:1g_aldl_schematic_simple.jpg]]  For applications requiring RS-232 signal levels to be within spec, a more comple…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="391" xml:space="preserve">For some applications, this passive schematic is enough:

[[Image:1g_aldl_schematic_simple.jpg]]

For applications requiring RS-232 signal levels to be within spec, a more complete cable is required:

[[Image:1g_aldl_schematic_complete.jpg]]

(Second image borrowed from the [http://mmcdlogger.sourceforge.net/ MMCd] website, a program which makes use of this cable for datalogging 1g DSMs.)</text>
    <sha1>0fbd2e904b2e34e7c20535faddcb154cf29e38ac</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Talk:EvoScan</title>
  <ns>1</ns>
  <id>259</id>
  <revision>
    <id>954</id>
    <timestamp>2010-02-06T16:38:07Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'I have a few problems with this page; it's basically an advertisement for EvoScan, rather than information that's useful to readers here. I suspect this could be cleaned up consi…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">I have a few problems with this page; it's basically an advertisement for EvoScan, rather than information that's useful to readers here. I suspect this could be cleaned up considerably, with a link back to the Limitless website for the marketing stuff. -- [[User:EdwardMarshall|logic]] 10:38, 6 February 2010 (CST)</text>
    <sha1>5042048d2ad174f704fdfb8df6d0ed02be7f5142</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>MUT Commands</title>
  <ns>0</ns>
  <id>229</id>
  <revision>
    <id>839</id>
    <parentid>838</parentid>
    <timestamp>2010-02-25T02:08:09Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1652" xml:space="preserve">MUT commands control a variety of solenoids, pumps, and other functions commanded by the ECU. These command IDs range from C0 through FF; IDs less than C0 are [[MUT Requests]], which correspond to locations in the MUT table.

&lt;center&gt;
{| border="3" cellspacing="2" cellpadding="5"
|- align="left"
!ID1
!Description
|-
|C0
|
|-
|C1
|
|-
|C2
|
|-
|C3
|SAS ([[Speed Adjusting Screw]])
for adjusting the amount of air allowed to bypass the throttle body when the ISC is not in use and the throttle plate is closed
|-
|C4
|
|-
|C5
|Purge solenoid venting
|-
|C6
|
|-
|C7
|
|-
|C8
|
|-
|C9
|
|-
|CA
|Invalid command
|-
|CB
|Invalid command
|-
|CC
|
|-
|CD
|A/C fan high
|-
|CE
|A/C fan low
|-
|CF
|Main fan high
|-
|D0
|Main fan low
|-
|D1
|
|-
|D2
|Lower RPM
|-
|D3
|Boost control solenoid
|-
|D4
|
|-
|D5
|EGR solenoid
|-
|D6
|Fuel pressure solenoid
|-
|D7
|Purge solenoid
|-
|D8
|Fuel pump
|-
|D9
|Fix timing at 5 degrees
|-
|DA
|Disable injector 1
|-
|DB
|Disable injector 2
|-
|DC
|Disable injector 3
|-
|DD
|Disable injector 4
|-
|DE
|Disable injector 5 (unused)
|-
|DF
|Disable injector 6 (unused)
|-
|E0
|
|-
|E1
|
|-
|E2
|
|-
|E3
|
|-
|E4
|
|-
|E5
|
|-
|E6
|
|-
|E7
|
|-
|E8
|
|-
|E9
|
|-
|EA
|
|-
|EB
|
|-
|EC
|Calibration F6A
|-
|ED
|Calibration
|-
|EE
|Calibration
|-
|EF
|Calibration
|-
|F0
|
|-
|F1
|
|-
|F2
|
|-
|F3
|Cancel previously-active command (ie. SAS mode)
|-
|F4
|
|-
|F5
|
|-
|F6
|
|-
|F7
|
|-
|F8
|
|-
|F9
|some keep alive function to keep the accuator engaged. response is 0xff
|-
|FA
|Clear active and stored faults
|-
|FB
|Force tests to run
|-
|FC
|Clear active faults
|-
|FD
|
|-
|FE
|Immobilizer
|-
|FF
|Init code
|}
&lt;/center&gt;</text>
    <sha1>7a8aa9c62bb2d95f02f5856d72634746f838672f</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>89960000</title>
  <ns>0</ns>
  <id>195</id>
  <revision>
    <id>760</id>
    <parentid>758</parentid>
    <timestamp>2010-04-26T21:00:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* RAM Addresses */  Add MUT location.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="470" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year: 2006

Market: JDM

Case id: 

Transmission: 6 speed

==Replacements==

==Download files==
[[Image:89960000_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;35920&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|89960000]]</text>
    <sha1>1252938a93cf704c7fba8e04970afcc9c2574847</sha1>
  </revision>
  <revision>
    <id>759</id>
    <parentid>758</parentid>
    <timestamp>2010-04-26T21:11:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* RAM Addresses */ Added 2-byte RPM and airflow.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="486" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year: 2006

Market: JDM

Case id: 

Transmission: 6 speed

==Replacements==

==Download files==
[[Image:89960000_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;35920&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6AEE&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6AEF&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B6E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B6F&lt;/tt&gt;

[[Category:ROMs|89960000]]</text>
    <sha1>430ab765005545b74fa925ea766ded8f51120020</sha1>
  </revision>
  <revision>
    <id>758</id>
    <timestamp>2010-04-27T14:23:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* RAM Addresses */ Add 2-byte load, thanks danieln!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="494" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year: 2006

Market: JDM

Case id: 

Transmission: 6 speed

==Replacements==

==Download files==
[[Image:89960000_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;35920&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6B12&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;6B13&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6AEE&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6AEF&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B6E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B6F&lt;/tt&gt;

[[Category:ROMs|89960000]]</text>
    <sha1>b4415846d067c040804dd96131a435e2338d015d</sha1>
  </revision>
  <revision>
    <id>761</id>
    <parentid>758</parentid>
    <timestamp>2010-04-27T14:23:54Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="575" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year: 2006

Market: JDM

Case id: 

Transmission: 6 speed

Discussion: http://forums.evolutionm.net/ecuflash/488795-89960000-any-info.html

==Replacements==

==Download files==
[[Image:89960000_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;35920&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;6B12&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;6B13&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;6AEE&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;6AEF&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;6B6E&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;6B6F&lt;/tt&gt;

[[Category:ROMs|89960000]]</text>
    <sha1>7981bbeb4132eb16e336a15d8db7d2ffd8fa0d92</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:Warning.gif</title>
  <ns>6</ns>
  <id>260</id>
  <revision>
    <id>955</id>
    <timestamp>2010-04-28T17:57:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:Notepad.gif</title>
  <ns>6</ns>
  <id>261</id>
  <revision>
    <id>956</id>
    <timestamp>2010-04-28T17:57:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Template:Warning</title>
  <ns>10</ns>
  <id>262</id>
  <revision>
    <id>958</id>
    <parentid>957</parentid>
    <timestamp>2010-04-28T17:58:08Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:3px;"&gt; [[Image:Warning.gif]] '''WARNING:''' {{{1}}} &lt;/div&gt;'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="124" xml:space="preserve">&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:3px;"&gt;
[[Image:Warning.gif]] '''WARNING:''' {{{1}}}
&lt;/div&gt;</text>
    <sha1>eb2233ae783fd5cb18eca281dcb4123bb1b6d90f</sha1>
  </revision>
  <revision>
    <id>959</id>
    <parentid>957</parentid>
    <timestamp>2010-04-28T18:00:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="132" xml:space="preserve">&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:10px;"&gt;
[[Image:Warning.gif]] '''WARNING!''' &lt;br /&gt; {{{1}}}
&lt;/div&gt;</text>
    <sha1>403445dc15fd9d4e5ca9e55006753cbd7c8f457e</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Template:Note</title>
  <ns>10</ns>
  <id>43</id>
  <revision>
    <id>146</id>
    <parentid>143</parentid>
    <timestamp>2010-04-28T17:58:38Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Replaced content with '&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif]] '''NOTE:''' {{{1}}}
&lt;/div&gt;'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif]] '''NOTE:''' {{{1}}}
&lt;/div&gt;</text>
    <sha1>4593dbed6819c4131f8fdfc1efdd201da250b0c8</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>27</id>
    <parentid>1</parentid>
    <timestamp>2010-04-28T18:02:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Formatting/style changes.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2410" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''Note to editors:''' if you're planning on adding a new page to the wiki, thank you for the help! But please, make sure you check to see if it doesn't already exist first. For example, we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. If the page you were going to add is already covered by an existing page, please help us improve by augmenting and cleaning up the existing articles. Thanks!


{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}


== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>6f77ed3adf6975655d3dbbb88ddb86b913067482</sha1>
  </revision>
  <revision>
    <id>26</id>
    <parentid>1</parentid>
    <timestamp>2010-05-02T00:54:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add note about the mirror directory.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2788" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

''Note to editors:'' if you're planning on adding a new page to the wiki, thank you for the help! But please, make sure you check to see if it doesn't already exist first. For example, we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. If the page you were going to add is already covered by an existing page, please help us improve by augmenting and cleaning up the existing articles. Thanks!


{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}


== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>5dfd509d510b436061deac1c0ac7b7d07a54ede9</sha1>
  </revision>
</page>
<page arvcontinue="20100105211301|867">
  <title>File:Monamona-cablle-schematic.pdf</title>
  <ns>6</ns>
  <id>263</id>
  <revision>
    <id>963</id>
    <timestamp>2010-05-03T15:22:41Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Plugs, Pins, and Connectors</title>
  <ns>0</ns>
  <id>242</id>
  <revision>
    <id>914</id>
    <parentid>881</parentid>
    <timestamp>2010-05-03T21:35:53Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* ACD ECU */ Add pin size information.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11148" xml:space="preserve">= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]. No, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. 

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.</text>
    <sha1>eebfb2b98dc662dee8a6b48cff0da8c188d07d44</sha1>
  </revision>
  <revision>
    <id>911</id>
    <parentid>881</parentid>
    <timestamp>2011-01-26T05:49:43Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Tried to clean up some of the blatant SEO that New United added to the page. They started off good, but by the time they reached the end, they were just puking links everywhere.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16202" xml:space="preserve">= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.


Play nice.


== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.


= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_10_116

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_127

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_554&amp;products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_771&amp;products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682</text>
    <sha1>4ea0b13328c3e8c5954a25cb6f5eb593dbd8ff69</sha1>
  </revision>
  <revision>
    <id>912</id>
    <parentid>881</parentid>
    <timestamp>2011-02-14T16:40:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo VIII and 2g DSM ECU */ Fix labeling error on VIII/2g pins.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16224" xml:space="preserve">= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.


Play nice.


== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.


= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_10_116

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_127

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_554&amp;products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_771&amp;products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682</text>
    <sha1>cde1ea92be9642717d2626bebf9847ab498de778</sha1>
  </revision>
  <revision>
    <id>915</id>
    <parentid>881</parentid>
    <timestamp>2011-02-14T16:44:51Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Evo IX ECU */ Add AWG info for IX pins.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16252" xml:space="preserve">= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.


Play nice.


== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.


= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_10_116

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_127

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''

: Small pins (tin, 18-20AWG), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

: Large pins (gold, 16-20AWG), '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_554&amp;products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_771&amp;products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682</text>
    <sha1>a9896022966a9f6372dd6b9199bcc65782af6595</sha1>
  </revision>
  <revision>
    <id>924</id>
    <parentid>923</parentid>
    <timestamp>2011-11-18T05:34:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Undo revision 1041 by [[Special:Contributions/Newunitedtech|Newunitedtech]] ([[User talk:Newunitedtech|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18570" xml:space="preserve">= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.


Play nice.


== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.


= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=247&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44495,44389,44395,44392,44378,44498,44500&amp;N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&amp;M=PPROP&amp;P=&amp;BML=10576,17560,17536,17534&amp;LG=1&amp;PG=1&amp;IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&amp;N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-1&amp;RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170352-2&amp;RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172771-2&amp;RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-1&amp;RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=170353-2&amp;RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-1&amp;RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&amp;M=BYPN&amp;TCPN=172772-2&amp;RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;search_in_description=1&amp;keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917975''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917975%7FA%7Fpdf%7FEnglish%7FENG_CD_917975_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917975-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=917975

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917981-1-ND
:: www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=917981

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=917989

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=917992

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&amp;DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=178780

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=175265

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&amp;keyword=175269

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2317-ND

''Pins:''

: Small pins (tin, 18-20AWG), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2320-ND

: Large pins (gold, 16-20AWG), '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;name=670-2319-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&amp;series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])


[new united race tech]
:i did a bit of research on these connectors, and they are compatible with the Amp / Tyco Multi-Lock 040/070 series.
:i am not sure if the JAE terminals will fit the Tyco parts or vice versa, but the plugs mate the same.
 
:part numbers can be found in the EVOIII 2g section

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, [http://www.newunitedracetech.com/ New United Race Tech] may have these in stock or can special-order them for you, and carries a large selection of other connectors.

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_554&amp;products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_552_553_771&amp;products_id=9836 

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_31&amp;products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

[new united race tech]
:These parts fall in to what we call "2.3 I" several connector companies make a compatible series
::Sumitomo MT Unsealed Series
::Yazaki 2.3 Unsealed Series 
::KET 090 Unsealed Series 

:it should also be noted, that you can find compatible upgraded parts in the "2.3 II" series.  
:they have a newer terminal design, and a secondary locking mechanism.  we suggest to our customers they move in to the 2.3II series if possible. 
::Sumitomo TS 090 Unsealed Series
::Yazaki 2.3II Unsealed Series
::KET 090II Unsealed Series

::  most of these should have a 5 digit number on the back of the connector, that can be helpful to find a vendor that can supply them to you.

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_36_166_39_41&amp;products_id=6897

: Pins Male and Female, separately (are interchangeable):
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=19_36_166_39_40

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940


: These Pins and Seals are compatible with the Yazaki 2.3II Sealed Series (if you cant find a TS terminal in stock anywhere)
::http://www.newunitedracetech.com/shop/index.php?main_page=index&amp;cPath=198_265_763_268_271

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682

[new united race tech]
:the TS 090 (2.3II) is a very popular series and is a made by many companies
:: Sumitomo TS Sealed Series
:: Yazaki 2.3II Series
:: KET KUM Furukawa JST and i hear Delphi all make are similar series, detail to come.
:: all of these will have a 5 digit number on the back of the housing, and can be used to identify the connector.

:also appears in the Sumitomo MT Sealed Series as well, but i suggest the newer TS series if you can get it.
: Keyway left Female
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_937_988_27&amp;products_id=5781

:keyway Right Female
::http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_937_988_27&amp;products_id=5783

:keyway Right Male
::http://www.newunitedracetech.com/shop/index.php?main_page=product_info&amp;cPath=19_25_937_988_27&amp;products_id=5780</text>
    <sha1>aa193a88b01f26e2865422f65fcd3b3152c65e6e</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>ECU Development</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>658</id>
    <parentid>647</parentid>
    <timestamp>2010-05-03T21:36:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1192" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf  schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>8860f6f15c443e289b467bc6fafaa6318250990e</sha1>
  </revision>
  <revision>
    <id>663</id>
    <parentid>658</parentid>
    <timestamp>2010-10-25T02:26:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Communications */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1211" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf  schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>8d89f48667b8cd379877bacd6cad19c4c9f4d587</sha1>
  </revision>
  <revision>
    <id>664</id>
    <parentid>663</parentid>
    <timestamp>2010-10-25T21:31:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Communications */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1233" xml:space="preserve">== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf  schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]
* [[OBD-II Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>fd815cc041fd44a0cbc7ad0f394f8978c6b661a5</sha1>
  </revision>
  <revision>
    <id>665</id>
    <parentid>664</parentid>
    <timestamp>2010-11-02T21:57:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Getting Started */ Add link to table-locating guide.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1255" xml:space="preserve">== Getting Started ==

* [[Development Tips]]
* [[Locating Tables]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf  schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]
* [[OBD-II Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)</text>
    <sha1>5549e250b210d357cbfcca4a3e7218ab111caf0d</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Template:Warning</title>
  <ns>10</ns>
  <id>262</id>
  <revision>
    <id>960</id>
    <parentid>957</parentid>
    <timestamp>2010-05-03T21:47:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="139" xml:space="preserve">&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:10px;"&gt;
[[Image:Warning.gif]] '''WARNING!''' &lt;br /&gt; &lt;br /&gt; {{{1}}}
&lt;/div&gt;</text>
    <sha1>fd822bbdf23a5cfb200b139502855183a0893d43</sha1>
  </revision>
  <revision>
    <id>961</id>
    <parentid>957</parentid>
    <timestamp>2010-05-04T02:30:42Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="170" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:10px;"&gt;
[[Image:Warning.gif|left]] '''WARNING!''' {{{1}}} &lt;br style="clear: both" /&gt;
&lt;/div&gt; &lt;br /&gt;</text>
    <sha1>a12063dcdd5ac42bee8f199d8114bd889600ceec</sha1>
  </revision>
  <revision>
    <id>962</id>
    <parentid>957</parentid>
    <timestamp>2010-05-04T02:31:31Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:10px;"&gt;
[[Image:Warning.gif|middle]] '''WARNING!''' {{{1}}} &lt;br style="clear: both" /&gt;
&lt;/div&gt; &lt;br /&gt;</text>
    <sha1>b36d4a923dd3c27ab14b3dc5857f6d20c7c09f07</sha1>
  </revision>
  <revision>
    <id>957</id>
    <timestamp>2010-05-04T02:31:46Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="170" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid red;background-color:#f9e9e9;padding:10px;"&gt;
[[Image:Warning.gif|left]] '''WARNING!''' {{{1}}} &lt;br style="clear: both" /&gt;
&lt;/div&gt; &lt;br /&gt;</text>
    <sha1>a12063dcdd5ac42bee8f199d8114bd889600ceec</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>USDM ACD Pinout</title>
  <ns>0</ns>
  <id>264</id>
  <revision>
    <id>964</id>
    <timestamp>2010-05-03T21:47:57Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '{{warning|This document is still being put together. Don't trust anything you read in here for now; check the [http://forums.evolutionm.net/ecuflash/473547-break-thru-reading-acd…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1628" xml:space="preserve">{{warning|This document is still being put together. Don't trust anything you read in here for now; check the [http://forums.evolutionm.net/ecuflash/473547-break-thru-reading-acd-ecu-ecuflash.html EvoM thread] or [http://evoscan.com/technical-vehicle-manuals/62-acd-ayc-sayc-at EvoScan website] for more details.}}

The USDM Evo VIII ACD ECU uses a two-plug harness, with two rows of pins for each plug. See the [[Plugs, Pins, and Connectors]] page for part numbers and further details.

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 31, 37, 38, 39, 51, and 52 (16 total) are "large" (ie. power); the remaining (32) pins are "small" (signal). Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|31||32||33||34||35||36||37||38||39||style="background-color: yellow"|40||style="background-color: yellow"|41
|-
|style="background-color: yellow"|42||43||44||45||46||47||48||49||50||style="background-color: yellow"|51||style="background-color: yellow"|52
|}
|}</text>
    <sha1>2d10aa90dac36d47085fe97bdf974881c9425993</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Template:Note</title>
  <ns>10</ns>
  <id>43</id>
  <revision>
    <id>147</id>
    <parentid>143</parentid>
    <timestamp>2010-05-04T02:20:31Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif]] '''NOTE:''' &lt;br /&gt; &lt;br /&gt; {{{1}}}
&lt;/div&gt;</text>
    <sha1>d924eaaf0cf9241633f05a8fdb1b9b7fa1f936e6</sha1>
  </revision>
  <revision>
    <id>145</id>
    <parentid>143</parentid>
    <timestamp>2010-05-04T02:22:12Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="148" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif]] '''NOTE:''' &lt;br /&gt; &lt;br /&gt; {{{1}}}
&lt;/div&gt;&lt;br /&gt;</text>
    <sha1>8890f67d883736bd27209d4ef4ca9a1c52455c2f</sha1>
  </revision>
  <revision>
    <id>144</id>
    <parentid>143</parentid>
    <timestamp>2010-05-04T02:25:10Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="141" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif|middle]] '''NOTE:''' {{{1}}}
&lt;/div&gt;&lt;br /&gt;</text>
    <sha1>27dfbd8882936c50acf0c4b3941f9b77d9d527ac</sha1>
  </revision>
  <revision>
    <id>143</id>
    <parentid>142</parentid>
    <timestamp>2010-05-04T02:29:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">&lt;br /&gt;&lt;div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;"&gt;
[[Image:Notepad.gif|left]] '''NOTE:''' {{{1}}} &lt;br style="clear: both" /&gt;
&lt;/div&gt; &lt;br /&gt;</text>
    <sha1>62bf546157980d7ad3db72a4c0472f394a86c9f4</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Immobilizer Disabling</title>
  <ns>0</ns>
  <id>150</id>
  <revision>
    <id>645</id>
    <parentid>643</parentid>
    <timestamp>2010-05-04T02:21:49Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2111" xml:space="preserve">Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:

* When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; the immobilizer code in 96530006 operates differently, and needs to be disabled when used on a USDM vehicle. (Update: this is no longer necessary for simply switching ROMs; see the first part of the [[96530006]] description for more details.)
* When the original immobilizer code has been lost due to user error, such as overwriting the original ROM on the vehicle with one found online without making a backup first.
* Your keyfob has been damaged, and the RFID tag can no longer be read properly by the ECU.

{{note|'''This information is provided solely to help you restore the operation of ''your own'' vehicle; this website's operators and authors do not endorse the use of this information for mischief or illegal purposes'''.}}

First, please read the page [[Periphery Configuration]]; you'll need to add the configuration information shown there to be able to do this. (This should no longer be necessary with newer versions of EcuFlash, although the periphery values are unlabeled.)

Once you've added that information, open EcuFlash and load your ROM. Scroll down to the "ECUPeriphery" section, and open the "ECU Periphery 0 (FAA) Bits" table. You should see a table of choices, one of which is "Immobilizer Enabled?", with a "1" in the column next to it. Select the field with "1" in it, and press the "[" key to change it to a "0" instead. You should see the entire bottom half of the column show an indication that it was changed; this is normal, because you're actually changing that whole byte of information, not just the bit you just edited.

After saving your work, simply upload your changes to the ECU as you normally would, and your immobilizer should now be disabled. To test, simply leave your car parked in a bad neighborhood overnight.

{{warning|Be aware that this disables an important security feature of your vehicle, and should not be done without understanding the full impact of the change.}}</text>
    <sha1>eeec546f101d004167c0bc2f51605d6c2024dbeb</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>22</id>
    <parentid>1</parentid>
    <timestamp>2010-05-04T02:30:59Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2786" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

''Note to editors:'' if you're planning on adding a new page to the wiki, thank you for the help! But please, make sure you check to see if it doesn't already exist first. For example, we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. If the page you were going to add is already covered by an existing page, please help us improve by augmenting and cleaning up the existing articles. Thanks!

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>958bb3678a5c3ab23bff5a6c5f23338ec453ef3e</sha1>
  </revision>
  <revision>
    <id>11</id>
    <parentid>1</parentid>
    <timestamp>2010-05-04T02:50:39Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2777" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

{{note|''Editors!'' if you're here to add a new page to the wiki, we appreciate the help! But please, check to see if it doesn't already exist first; we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. Just search for your topic in the sidebar, and see if there's something similar already; if there is, please help us improve by augmenting and cleaning up existing articles. Thanks!}}

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>983a7ec324fdc2de151e03d238cfb94e0fcdaf6c</sha1>
  </revision>
  <revision>
    <id>35</id>
    <parentid>1</parentid>
    <timestamp>2011-09-30T00:27:52Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Quencha8760|Quencha8760]] ([[User talk:Quencha8760|talk]]) to last revision by [[User:EdwardMarshall|EdwardMarshall]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2777" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

{{note|''Editors!'' if you're here to add a new page to the wiki, we appreciate the help! But please, check to see if it doesn't already exist first; we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. Just search for your topic in the sidebar, and see if there's something similar already; if there is, please help us improve by augmenting and cleaning up existing articles. Thanks!}}

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>983a7ec324fdc2de151e03d238cfb94e0fcdaf6c</sha1>
  </revision>
  <revision>
    <id>31</id>
    <parentid>1</parentid>
    <timestamp>2011-10-07T00:30:02Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Luckiong754|Luckiong754]] ([[User talk:Luckiong754|talk]]) to last revision by [[User:EdwardMarshall|EdwardMarshall]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2777" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

{{note|''Editors!'' if you're here to add a new page to the wiki, we appreciate the help! But please, check to see if it doesn't already exist first; we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. Just search for your topic in the sidebar, and see if there's something similar already; if there is, please help us improve by augmenting and cleaning up existing articles. Thanks!}}

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>983a7ec324fdc2de151e03d238cfb94e0fcdaf6c</sha1>
  </revision>
  <revision>
    <id>1</id>
    <timestamp>2016-01-10T23:30:54Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="592" xml:space="preserve">&lt;strong&gt;MediaWiki has been successfully installed.&lt;/strong&gt;

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]</text>
    <sha1>8e0aa2f2a7829587801db67d0424d9b447e09867</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>How to Tune an Evo TB Alternate</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>450</id>
    <parentid>449</parentid>
    <timestamp>2010-05-04T02:32:26Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Boost control tables */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43456" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[[EcuFlash]]- Yes, let's assume you need the tuning software to tune your ECU. This software is a free download.

===Logging Software===
[[EvoScan]]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.

''(As of 8/15/08, LogWorks 3 does not include the OpenPort plugin needed to support the OpenPort cable used for logging an Evo.  You must install a version of LogWorks 2 that includes this plugin.)''

Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[[Logging Cable]] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors. This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they only give accurate feedback at [http://en.wikipedia.org/wiki/Air-fuel_ratio stoich] (1 Lambda (λ), or 14.7:1 AFR for gasoline).  This is because the ECU only uses data from these sensors in "closed loop" mode.

'''Closed loop''' means that the ECU references a signal from a sensor and compares it to a target value in the ROM, and can then make adjustments to values on-the-fly to reach that target.  The stock ECU uses closed loop fueling at low load levels (idle, cruise) and the AFR target is 14.7:1, or 0.5v on the front O2 sensor.  Stock boost control is also closed loop ... the ECU targets a specific load level for a given RPM and can adjust the duty cycle of the boost control solenoid for correction.  More on that later.

There are crossover points defined (based on RPM, load and TPS voltage) that tell the ECU when to stop using closed loop fueling and switch to "open loop." '''Open loop''' occurs when the vehicle stops relying on sensors to give feedback and simply "trusts" the defined maps to be correct. In the case of AFR, the ECU used the data in the fuel maps and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing an extra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher voltage range of the sensor and it's linear response allows for more accurate readings.

Here are some choices for a [[Wide Band Air Fuel Meter]]

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately record boost levels with your logs. This should give the same readings as your mechanical boost gauge, but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get some info in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most up-to-date Evo IX ROM.  For info on the most up-to-date, supported ROMs, check the [[Downloads|downloads page]].

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit, and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store misc. tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 reference values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustration below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the fuel value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not.

===ECU-Based Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route as you can use the stock boost control solenoid.

With this method you retain the ECU's closed loop control of the turbo system which allows for some options you can't get from most manual/electronic boost controllers. Mrfred has really gotten dirty with this functionality in the ROM and has found different ways of controlling the boost level with the stock ECU.  Read about those discoveries here and here (EvoM currently down).

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

This method works with the modified stock boost control solenoid or other aftermarket 3-port boost control solenoids.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. The "Boost Limit" and "Boost Delay Timer" tables still function with a manual or electronic boost controller, so you'll need to adjust them as noted below.

===Controlling boost with the ECU===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

If you plan to use the stock BCS, read [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control]. You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

If you are using an aftermarket 3-port BCS you will remove the stock lines and the stock restrictor pills during the install.  They are not needed for a 3-port solenoid setup.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu.

{{warning|Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.}}

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the ECU will cut fuel to protect the engine.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.  If using Mrfred's PSI-based boost control, this table is not used.  You will add another table with scaling in PSI.  The new table will function the same as this one.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.  Again, when using PSI-based boost control you will create another error correction table with PSI scaling.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.  For PSI-based boost control, you will create another set of these tables with PSI scaling.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
This map, also referred to as "Baseline Wastegate Duty," determines the initial duty cycle values of the BCS.  If the actual load/PSI is not equal to the desired values in the desired boost table, the error correction values kick in and make adjustments based on the values here.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill/3-port solenoid installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill/3-port solenoid before flashing the ECU with your new boost settings!

====Boost Delay Timer====
This map can stay where it is,but you can increase it if you feel the need.

====Boost Control Load Offset====
Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

====Turbo Boost Error Correction====
You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

====Boost Desired Engine Load====
There are 3 of these maps, and sadly, I have no idea why. So, the easiest way to proceed is to modify all 3 of the maps.  This will ensure that you have the desired boost settings in any sutuation.

Set the BDEL in all 3 maps to "140" with a taper down to "100" from 5500 RPM to 7000 RPM. This value added to the load offset value of "100" gives you a desired load of "240" through most of the rev band, which is equal to about 22 psi in most cases. We're tapering down the top end to reduce heat and the chance of knock.

====Max Wastegate Duty====
Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.

Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

====Boost Limit====
Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

====Min Temp for Full Boost Control====
This table is incorrectly defined, so leave it alone.  Stock value is "85."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable if it isn't consistent. Knock counts higher than 3 (actually, 1 on a IX) begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location or by increasing the octane of your fuel. If the knock occurs in additional logs in the same RPM/load area even with higher octane fuel, then it is real knock and you need to adjust your maps to compensate.  Phantom knock is very rare on lightly modified vehicles and should not be assumed without proper validation.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels which (for the most part) are parallel to your boost levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3 and boost is conservative, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at -2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for low load, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, the less stable it is under pressure and therefore more likely to burn in an unstable manner causing detonation or pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

'''The values in the fuel map are not actual AFR values.''' They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This affects your tuning by throwing off the values even in the fuel map even more and causing shifts in AFR between gears. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should show an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12s up to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and '''make small, gradual changes'''. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways, such as more boost, a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute timing advance number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the burning fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://en.wikipedia.org/wiki/Dynamometer dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of flat road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car and close the gap by .004 every 50 hp.  This means increased boost, an open filter and exhaust on an average Evo could call for a colder plug.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

The Evo IX comes with a colder plug than the VIII so basic mods on the IX don't require a plug change.  The standard, colder replacement plugs for the VIII are the BR7ES (1/2 step colder) and BPR8ES (1 step colder).

For more info on plugs, [http://sevo.motionforum.net/engine-turbo-f10/spark-plugs-t116.htm check here].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>c45cc02cfccc62335eb713cfbc0a98d973481a82</sha1>
  </revision>
  <revision>
    <id>451</id>
    <parentid>450</parentid>
    <timestamp>2010-05-04T02:32:44Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* What you need to modify */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43449" xml:space="preserve">Original Thread by Touring Bubble: &amp;nbsp;[forum now closed - original posting date04-30-2007]&lt;br&gt;http://www.evolutionse.com/forums/showthread.php?t=3014&lt;br&gt;&lt;br&gt;Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;cd=9&amp;amp;gl=us&amp;amp;client=firefox-a Here]
&lt;br&gt;
 Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[[EcuFlash]]- Yes, let's assume you need the tuning software to tune your ECU. This software is a free download.

===Logging Software===
[[EvoScan]]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.

''(As of 8/15/08, LogWorks 3 does not include the OpenPort plugin needed to support the OpenPort cable used for logging an Evo.  You must install a version of LogWorks 2 that includes this plugin.)''

Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[[Logging Cable]] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors. This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they only give accurate feedback at [http://en.wikipedia.org/wiki/Air-fuel_ratio stoich] (1 Lambda (λ), or 14.7:1 AFR for gasoline).  This is because the ECU only uses data from these sensors in "closed loop" mode.

'''Closed loop''' means that the ECU references a signal from a sensor and compares it to a target value in the ROM, and can then make adjustments to values on-the-fly to reach that target.  The stock ECU uses closed loop fueling at low load levels (idle, cruise) and the AFR target is 14.7:1, or 0.5v on the front O2 sensor.  Stock boost control is also closed loop ... the ECU targets a specific load level for a given RPM and can adjust the duty cycle of the boost control solenoid for correction.  More on that later.

There are crossover points defined (based on RPM, load and TPS voltage) that tell the ECU when to stop using closed loop fueling and switch to "open loop." '''Open loop''' occurs when the vehicle stops relying on sensors to give feedback and simply "trusts" the defined maps to be correct. In the case of AFR, the ECU used the data in the fuel maps and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing an extra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher voltage range of the sensor and it's linear response allows for more accurate readings.

Here are some choices for a [[Wide Band Air Fuel Meter]]

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately record boost levels with your logs. This should give the same readings as your mechanical boost gauge, but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get some info in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning&amp;#33; [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most up-to-date Evo IX ROM.  For info on the most up-to-date, supported ROMs, check the [[Downloads|downloads page]].

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit, and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store misc. tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 reference values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustration below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the fuel value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not.

===ECU-Based Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route as you can use the stock boost control solenoid.

With this method you retain the ECU's closed loop control of the turbo system which allows for some options you can't get from most manual/electronic boost controllers. Mrfred has really gotten dirty with this functionality in the ROM and has found different ways of controlling the boost level with the stock ECU.  Read about those discoveries here and here (EvoM currently down).

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

This method works with the modified stock boost control solenoid or other aftermarket 3-port boost control solenoids.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. The "Boost Limit" and "Boost Delay Timer" tables still function with a manual or electronic boost controller, so you'll need to adjust them as noted below.

===Controlling boost with the ECU===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&amp;amp;postcount=7 this post] if you want to learn more.

If you plan to use the stock BCS, read [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control]. You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

If you are using an aftermarket 3-port BCS you will remove the stock lines and the stock restrictor pills during the install.  They are not needed for a 3-port solenoid setup.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu.

{{warning|Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.}}

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the ECU will cut fuel to protect the engine.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM.  If using Mrfred's PSI-based boost control, this table is not used.  You will add another table with scaling in PSI.  The new table will function the same as this one.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -&amp;gt; desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load.  Again, when using PSI-based boost control you will create another error correction table with PSI scaling.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control.  For PSI-based boost control, you will create another set of these tables with PSI scaling.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
This map, also referred to as "Baseline Wastegate Duty," determines the initial duty cycle values of the BCS.  If the actual load/PSI is not equal to the desired values in the desired boost table, the error correction values kick in and make adjustments based on the values here.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill/3-port solenoid installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

{{warning|Do not drive the car with the modified boost pill/3-port solenoid before flashing the ECU with your new boost settings!}}

====Boost Delay Timer====
This map can stay where it is,but you can increase it if you feel the need.

====Boost Control Load Offset====
Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

====Turbo Boost Error Correction====
You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

====Boost Desired Engine Load====
There are 3 of these maps, and sadly, I have no idea why. So, the easiest way to proceed is to modify all 3 of the maps.  This will ensure that you have the desired boost settings in any sutuation.

Set the BDEL in all 3 maps to "140" with a taper down to "100" from 5500 RPM to 7000 RPM. This value added to the load offset value of "100" gives you a desired load of "240" through most of the rev band, which is equal to about 22 psi in most cases. We're tapering down the top end to reduce heat and the chance of knock.

====Max Wastegate Duty====
Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.

Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

====Boost Limit====
Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

====Min Temp for Full Boost Control====
This table is incorrectly defined, so leave it alone.  Stock value is "85."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable if it isn't consistent. Knock counts higher than 3 (actually, 1 on a IX) begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location or by increasing the octane of your fuel. If the knock occurs in additional logs in the same RPM/load area even with higher octane fuel, then it is real knock and you need to adjust your maps to compensate.  Phantom knock is very rare on lightly modified vehicles and should not be assumed without proper validation.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels which (for the most part) are parallel to your boost levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3 and boost is conservative, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at -2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for low load, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, the less stable it is under pressure and therefore more likely to burn in an unstable manner causing detonation or pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

'''The values in the fuel map are not actual AFR values.''' They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This affects your tuning by throwing off the values even in the fuel map even more and causing shifts in AFR between gears. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should show an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12s up to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and '''make small, gradual changes'''. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways, such as more boost, a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute timing advance number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the burning fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://en.wikipedia.org/wiki/Dynamometer dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of flat road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car and close the gap by .004 every 50 hp.  This means increased boost, an open filter and exhaust on an average Evo could call for a colder plug.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&amp;amp;AAIA=1432585 here is a list of plugs that will work].

The Evo IX comes with a colder plug than the VIII so basic mods on the IX don't require a plug change.  The standard, colder replacement plugs for the VIII are the BR7ES (1/2 step colder) and BPR8ES (1 step colder).

For more info on plugs, [http://sevo.motionforum.net/engine-turbo-f10/spark-plugs-t116.htm check here].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===</text>
    <sha1>214e4a2307173c86ae4b22831fe08baa5f117717</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Logging Cable</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>322</id>
    <parentid>318</parentid>
    <timestamp>2010-05-04T02:43:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1575" xml:space="preserve">There are a few cables that can be used to log and reflash data on Mitsubish ECUs:

* OpenPort 1.0 (no longer available)

* OpenPort 1.2 (no longer available)

* OpenPort 1.3M (no longer available)

* OpenPort 1.3D (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables]
** Datalogging only; no flashing support at all (needed physical wiring is not present). Low-cost logging option.

* OpenPort 1.3R (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables]
** Physically identical to OpenPort 1.3U, but without a license for use with EcuFlash; only Evo 7/8 vehicles can be flashed with this cable, using EvoScan. Lower-cost than 1.3U.

* OpenPort 1.3U (only available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables])
** Full-featured flashing/datalogging cable. Works with most loggers, as well as EcuFlash.

* OpenPort 2.0 (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables] or [http://www.tactrix.com tactrix.com])
** Newest version of full-featured cable; is now a device which supports CAN-bus vehicles such as the Evo X. Requires newer version of EcuFlash, and some loggers have not added support for it yet (EvoScan works).

There have been quite a few additional cables produced over the years that EvoScan supports, but typically only Tactrix-licensed cables will operate with EcuFlash.

See [[ECU Development]] for schematics for the OpenPort 1.0, 1.2, and 1.3U cables, as well as pinouts for the Evo ECUs, OBD-II, and diag plugs, and other useful electronics information.</text>
    <sha1>698fd1892b0ecd467caa1dc2ea2a450cc215947b</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>EvoScan</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>344</id>
    <parentid>342</parentid>
    <timestamp>2010-05-04T02:45:37Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Cleaned out marketing stuff. Seriously?</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6265" xml:space="preserve">&lt;br&gt;[http://www.evoscan.com/ EvoScan] is a program created by [http://forums.evolutionm.net/member.php?find=lastposter&amp;t=361521 Evo4Mad (Hamish)]. The program connects to the ECU via an OpenPort 1.3U or OpenPort 2.0 USB Cable [[Logging Cable]]. EvoScan allows you to log ECU data and also has the ability to connect to and log from a [[Wide Band Air Fuel Meter]].

=== Problems with the Map Tracer Feature ===

''' Logged Items '''

Unfortunately EvoScan bases this chart off of ECULoad (or LoadCalc, in some cases) and standard RPM.  If you are using the 1 byte load mod or 2 byte RPM you can run into issues.

''' Incorrect XML Definitions '''

You can also run into issues if your XMLs are incorrectly defined in the Evoscan XML directory.  It is often easiest to simply remove all unnecessary tables from the EvoScan definition files to ensure that you will not run into any snags.  You can also add Alt-map tables (which are not included by default) and/or Big-Map tables for newer versions of the [[TephraMod]].

''' How to: For problematic map tracers or BigMap tracing '''

EvoM user [http://forums.evolutionm.net/members/55720-fostytou.html Fostytou] details this method in a thread [http://forums.evolutionm.net/7078367-post16.html here] and [http://forums.evolutionm.net/7078461-post18.html here] and further down.

Essentially [http://forums.evolutionm.net/7447843-post15.html all you are going to do] is make sure everything is properly defined for your rom, and as minimalistically as possible.

:* 1) Get loadCalc values in your log.  The first time I did this I copied the load1byte column to to a column with "LoadCalc" in the header in the EvoScan XML (be sure to delete the old "LoadCalc" column.) (You can also just make a copy of the log and rename the load1byte or do as others have suggested and rename it in evoscan). This is silly because it allows you to then select which column you want to use for load. I assume if you log loadcalc or forced evoscan to populate it with 0 in each entry you would then be able to just select the correct load column.
:** More progress... Unfortunately you can't just have evoscan write a first and last entry of 0 with calc/priority 100. No matter what is selected in the drop down tracer is looking for loadcalc. You have 2 options:
:** 1) Rename the logged item for load1byte to "loadcalc" (less data, but could be confusing in the future)
:** 2) Replace your loadcalc and 1ByteLoad evoscan entry with these 2. Log the DEAD version. This should not really have an impact on performance, just create a very slightly larger log.
{|border="1" cellspacing="0"
|&lt;nowiki&gt;&lt;DataListItem DataLog="N" Color="" Display="Load Calculated REAL" LogReference="LoadCalcXXX" RequestID="29" Eval="5*[InjectorScaling]*((0.256*x)-(-0.1026*[Battery]+1.8741))/(14.7*128/[AFRMAP])" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="This is just an extended calculation to forumulate the real Load value beyond that shown in ECULoad.  A more accurate method is to reflash your ecu with a ROM mod that allows you to log 2Byte Load.&amp;#xD;&amp;#xA;&amp;#xD;&amp;#xA;Dont forget to update the InjectorScaling on the Main Form, with your injector scaling value used for your rom.&amp;#xD;&amp;#xA;&amp;#xD;&amp;#xA;5*InjScaling*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP]" Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;	&lt;DataListItem DataLog="N" Color="" Display="Load Calculated DEAD" LogReference="LoadCalc" RequestID="CALC" Eval="[Load1B]" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="Fake Load to get map tracer to work." Priority="1" Visible="False" /&gt;&lt;/nowiki&gt;
|}
&lt;br&gt;
:* 2) Modify an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
{|border="1" cellspacing="0"
|&lt;nowiki&gt;	&lt;table name="High Octane Fuel Map - ALT" category="Fuel" address="49b4d" type="3D" swapxy="true" scaling="AFR"&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;  &lt;table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;   &lt;table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt;  &lt;/table&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="High Octane Ignition Map 1 - ALT" category="Timing" address="49c8d" type="3D" swapxy="true" scaling="Timing"&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="Engine Load" address="6f2c" type="X Axis" elements="21" scaling="Load"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="RPM" address="6efa" type="Y Axis" elements="20" scaling="RPM"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;/table&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="High Octane Fuel Map" category="Fuel"  address="2dbd" type="3D" swapxy="true" scaling="AFR"&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;/table&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="High Octane Ignition Map 1" category="Timing" address="33e9" type="3D" swapxy="true" scaling="Timing"&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="Engine Load" address="6f2c" type="X Axis" scaling="Load" elements="21"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;table name="RPM" address="6efa" type="Y Axis" scaling="RPM" elements="20"/&gt;&lt;/nowiki&gt;
|-
|&lt;nowiki&gt; &lt;/table&gt;&lt;/nowiki&gt;
|}
:** An 88590715 example file is [[File:EVOSCAN_TephraMOD-88590715_ALT.zip]] .  These files go in your C:\Program Files\EvoScan\EvoScan v2.6\ROMS directory
&lt;br&gt;
:* 3) Open EvoScan MAP Tracer and pick your log file. 
:* 4) Right-click on the bottom and click "Load HEX and XML files." 
:** The first file you load is the ROM XML file you copied from ECUFlash. This would be the 88590715.xml file that you just made, and if it works properly it should load automatically from now on when you select your ROM.
:** The second file is your actual .hex/.bin ECUFlash flash file (your current tune or the one you were using when the log file was created). If you don't have one, you will have to use ECUFlash to connect to your ECU and download whatever tune you currently have.
:* 5) Now everything should be loaded and you can click on the parameters on the left to view them.</text>
    <sha1>a33e4c24219422e28ea521f63b8bf1814c133d77</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>MediaWiki:Common.css</title>
  <ns>8</ns>
  <id>265</id>
  <revision>
    <id>965</id>
    <timestamp>2010-06-28T17:45:21Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with '/* Pad Google AdSense box in portlet in sidebar */ #p-googleadsense .pBody {     padding-top: 5px;     text-align:  center; }'</comment>
    <model>css</model>
    <format>text/css</format>
    <text bytes="125" xml:space="preserve">/* Pad Google AdSense box in portlet in sidebar */
#p-googleadsense .pBody {
    padding-top: 5px;
    text-align:  center;
}</text>
    <sha1>483d7890732d50e0d6c97d62d64e1af057d7772a</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Help:Contents</title>
  <ns>12</ns>
  <id>4</id>
  <revision>
    <id>65</id>
    <parentid>62</parentid>
    <timestamp>2010-08-23T02:13:25Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Jsmith|Jsmith]] ([[User talk:Jsmith|talk]]) to last revision by [[User:EdwardMarshall|EdwardMarshall]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1567" xml:space="preserve">{{PD Help Page}}
==Reading==
* [[Help:Navigation|Navigation]]
* [[Help:Searching|Searching]]
* [[Help:Tracking changes|Tracking changes]]
* [[Help:Watchlist|Watchlist]]

==Editing==
* [[Help:Editing pages|Editing pages]]
* [[Help:Starting a new page|Starting a new page]]
* [[Help:Formatting|Formatting]]
* [[Help:Links|Links]]
* [[Help:User page|User pages]]
* [[Help:Talk pages|Talk pages]]

===Advanced editing===
* [[Help:Images|Images]]
* [[Help:Tables|Tables]]
* [[Help:Categories|Categories]]
* [[Help:Subpages|Subpages]]
* [[Help:Managing files|Managing files]]
* [[Help:Moving a page|Moving a page]]
* [[Help:Redirects|Redirects]]
* [[Help:Deleting a page|Deleting a page]]
* [[Help:Protected pages|Protected pages]]

* [[Help:Templates|Templates]]
* [[Help:Variables|Variables]]
* [[Help:Namespaces|Namespaces]]

* [[Help:Special pages|Special pages]]
* [[Help:External searches|External searches]]

===Personal customization===
* [[Help:Preferences|Preferences]]
* [[Help:Skins|Skins]]

==Wiki administration==

* [[Help:Sysops and permissions|Sysops and permissions]]

The following features require extra permissions that are not normally granted to all wiki users.

* [[Help:Protecting and unprotecting pages|Protecting and unprotecting pages]]
* [[Help:Sysop deleting and undeleting|Sysop deleting and undeleting]]
* [[Help:Patrolled edits|Patrolled edits]]
* [[Help:Blocking users|Blocking users]]
* [[Help:Range blocks|Range IP blocks]]
* [[Help:Assigning permissions|Assigning permissions]]

{{Languages|Help:Contents}}
[[Category:Help| ]]
__NOTOC__</text>
    <sha1>5bf86078783a83dfdfb7dd81571ba2724eb9f91e</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>EcuFlash</title>
  <ns>0</ns>
  <id>67</id>
  <revision>
    <id>244</id>
    <parentid>243</parentid>
    <timestamp>2010-09-16T16:14:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3386" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** Original command-line version, Subarus only. Source for this version was released, as well as for the 0.93 HC16 kernel.
* 0.91
** First support for 1.2 cables. I still have/use one. 
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2006-01-17
** First GUI version. I only have the executable, and it might not be the official one at that.
* 1.21
* 1.22
* 1.23
* 1.24
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26]
** First official Mitsubishi support.
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28]
** First Evo IX support.
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30]
** First release with an obscured executable. Change of heart from a few months prior, yet "About" text still asks for donations. Nice.
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31]
** First read-only H8 support, first MacOS release.
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]
* 1.33
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35]
** First support for "blobbits", ie. for periphery bit editing.
* 1.36
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37]
** First OpenPort 2.0 support.
* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483]
** First Evo X support, H8 support for 1.3 cables removed.
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595]
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31
* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03</text>
    <sha1>cdd854b246be6d320d3ab04046a7e936c880a0db</sha1>
  </revision>
  <revision>
    <id>238</id>
    <timestamp>2010-10-20T19:22:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7864" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** Original command-line version, Subarus only. [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91
** First support for OpenPort 1.2 cables.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2006-01-17
** First GUI version. We only have the executable, and it might not be the official one at that.

* 1.21, 2006-04-15

* 1.22, 2006-04-??

* 1.23, 2006-04-29
** user selectable color legends in the options menu 
** cut and paste to Excel and between maps 
** multiple selection using click, drag, ctrl-click, etc. 
** cell highlighting to show changes from original ROM 
** infinite undo / redo on a per map basis (might limit this in the future if memory becomes a problem) 
** increment / decrement (amount is defined in the scalings) 
** 1% increase / decrease (may have no effect if the display equation is too granular) 
** set / add / multiply (you can actually enter arbitrary equations as a function of "d" at the "set" prompt - e.g. d="d*2+1") 
** horizontal / vertical / 2-D interpolation 
** revert selected area to original values 

* 1.24

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26]
** First official Mitsubishi support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28]
** First Evo IX support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org 
** Added some Mitsubishi ROM definitions 
** Added auto-selection of OpenPort cables 
** Added descriptive icons to tables in metadata view 
** Fixed bug with tables having 2 generations of parents 
** Fixed bug with incorrect XMLID in new ROM wizard 
** Added ability to load a ROM file from the command line 
** Improved color scaling handling 
** Changed table to show only units for main data 
** Improved table layout 
** Added help text to tables 
** Fix metadata ordering to match XML file order 
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. Change of heart from a few months prior, yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31]
** First read-only H8 support, first MacOS release.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35]
** First support for "blobbits", ie. for periphery bit editing.

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483]
** First Evo X support, H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03</text>
    <sha1>06cd2ce3d9bd987436f97096894fe5c18d804698</sha1>
  </revision>
  <revision>
    <id>239</id>
    <parentid>238</parentid>
    <timestamp>2010-10-20T19:27:50Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8010" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** Original command-line version, Subarus only. [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91
** First support for OpenPort 1.2 cables.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2006-01-17
** First GUI version. We only have the executable, and it might not be the official one at that.

* 1.21, 2006-04-15

* 1.22, 2006-04-??

* 1.23, 2006-04-29
** user selectable color legends in the options menu 
** cut and paste to Excel and between maps 
** multiple selection using click, drag, ctrl-click, etc. 
** cell highlighting to show changes from original ROM 
** infinite undo / redo on a per map basis (might limit this in the future if memory becomes a problem) 
** increment / decrement (amount is defined in the scalings) 
** 1% increase / decrease (may have no effect if the display equation is too granular) 
** set / add / multiply (you can actually enter arbitrary equations as a function of "d" at the "set" prompt - e.g. d="d*2+1") 
** horizontal / vertical / 2-D interpolation 
** revert selected area to original values 

* 1.24

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26]
** First official Mitsubishi support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28]
** First Evo IX support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org 
** Added some Mitsubishi ROM definitions 
** Added auto-selection of OpenPort cables 
** Added descriptive icons to tables in metadata view 
** Fixed bug with tables having 2 generations of parents 
** Fixed bug with incorrect XMLID in new ROM wizard 
** Added ability to load a ROM file from the command line 
** Improved color scaling handling 
** Changed table to show only units for main data 
** Improved table layout 
** Added help text to tables 
** Fix metadata ordering to match XML file order 
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31]
** First read-only H8 support, first MacOS release.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35]
** First support for "blobbits", ie. for periphery bit editing.

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483]
** First Evo X support, H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03</text>
    <sha1>79df67790e58be5356852538173a967cf01f23cb</sha1>
  </revision>
  <revision>
    <id>241</id>
    <parentid>239</parentid>
    <timestamp>2010-10-20T19:59:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8456" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** Original command-line version, Subarus only. [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91
** First support for OpenPort 1.2 cables.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2006-01-17
** First GUI version. We only have the executable, and it might not be the official one at that.

* 1.21, 2006-04-15

* 1.22, 2006-04-??

* 1.23, 2006-04-29
** user selectable color legends in the options menu 
** cut and paste to Excel and between maps 
** multiple selection using click, drag, ctrl-click, etc. 
** cell highlighting to show changes from original ROM 
** infinite undo / redo on a per map basis (might limit this in the future if memory becomes a problem) 
** increment / decrement (amount is defined in the scalings) 
** 1% increase / decrease (may have no effect if the display equation is too granular) 
** set / add / multiply (you can actually enter arbitrary equations as a function of "d" at the "set" prompt - e.g. d="d*2+1") 
** horizontal / vertical / 2-D interpolation 
** revert selected area to original values 

* 1.24

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26]
** First official Mitsubishi support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28]
** First Evo IX support.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org 
** Added some Mitsubishi ROM definitions 
** Added auto-selection of OpenPort cables 
** Added descriptive icons to tables in metadata view 
** Fixed bug with tables having 2 generations of parents 
** Fixed bug with incorrect XMLID in new ROM wizard 
** Added ability to load a ROM file from the command line 
** Improved color scaling handling 
** Changed table to show only units for main data 
** Improved table layout 
** Added help text to tables 
** Fix metadata ordering to match XML file order 
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31]
** First read-only H8 support, first MacOS release.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35], 2007-05-15
** this is a minor update to support some recent cable changes - a major release is coming soon!
** FTDI drivers updated to CDM 2.02.06
** Qt updated to 4.4.0
** Qwt updated to 5.1.0
** bitfields now supported in bloblists ("blobbits", ie. for periphery bit editing)
** Subaru definitions update to merchgod's 0.8 release 

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* 1.40.2173

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483], 2009-01-29
** EcuFlash Related Changes
*** add support for EVO X CAN reflash
*** add DTC clear option for Evo X
*** add flash recovery mode option and flash recovery mode for Evo X
*** H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03</text>
    <sha1>c78a809ab0471fcf4aa82b0cf16c6fe7b264eee9</sha1>
  </revision>
  <revision>
    <id>245</id>
    <parentid>243</parentid>
    <timestamp>2010-10-20T20:20:21Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11735" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** First official release
** Command line supports read / flash / compare
** Supports 2001-2005 WRXs
** [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91, 2005-10-25
** This version has been created to support the new OpenPort 1.2. The OpenPort 1.2 has a 12V reflashing voltage that is controlled by RTS line of the virtual serial port which is off by default. EcuFlash now switches this voltage on at the appropriate times.
** This is intended to be the last command line version of EcuFlash. Future versions under development use a GUI and are supported under Windows / OS-X / linux.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2005-11-14
** First GUI version of EcuFlash using the [http://trolltech.com/ Qt Toolkit]
** (We only have the executable, and it might not be the official one at that.)

* 1.21, 2006-04-15
** Add support for drive by wire Subarus (STi,Forrester XT,Legacy GT,Baja,2006+ WRX)
** Switch to 'Mac' styled UI
** Add table view / editing with infinite undo
** Add user definable color maps
** Make 68HC916Y5 (WRX) kernel deal with bad serial data better

* 1.22, 2006-04-16
** Add flipx/flipy to axes widgets
** Change default color map

* 1.23, 2006-04-29
** Fix bug in SH7055 kernel that caused incorrect FMCLR register to be chosen
** Table checkboxes now single click and only hot within checkbox

* 1.24, 2006-04-30
** Fix bug causing crash when ROM images are closed out of order

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25], 2006-05-01
** Add user level option to hide obscure tables

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26], 2006-05-10
** This is the first version to officially support Mitsubishi vehicles (Evo 7/8,Eclipse,Lancer). Some ROM definitions are included, more will be added later
** Added driver installer to EcuFlash installation
** Installer backs up your current metadata to 'backupXXX'
** Removed option to delete maps until it works
** Added a needed checksum module for DBW Subarus
** Added support for float and double data types in scalings
** Added idle category
** Improved help in scalings editor
** Adaptive cell sizing in tables
** Map windows have ROM file in the title
** Added procedure steps for connecting to Mitsubishis
** Added directory browsing to options

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27], 2006-05-15
** Some new maps added to Evos
** Improved programming voltage messages for Subaru
** Fixed bug in tracking open map views when metadata view changed
** Expanded table cell sizing a bit to prevent ellipses

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28], 2006-06-20
** Evo 9 reflash support added
** Eclipse AT reflash support added
** Evo 9 map support improved
** Update all Mitsubishi XML definitions to use new reflash tool names
** Improved cell sizing further
** Fix problem of options changing when browsing options menus and canceling
** Add support for hex data entry when editing
** Switch to Qt 4.1.3
** Remove need for C runtime DLLs
** Fix update logic when editing map definitions
** Reset reference ROM data when reading a ROM
** Fix crash on edit of table with no parent

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org 
** Added some Mitsubishi ROM definitions 
** Added auto-selection of OpenPort cables 
** Added descriptive icons to tables in metadata view 
** Fixed bug with tables having 2 generations of parents 
** Fixed bug with incorrect XMLID in new ROM wizard 
** Added ability to load a ROM file from the command line 
** Improved color scaling handling 
** Changed table to show only units for main data 
** Improved table layout 
** Added help text to tables 
** Fix metadata ordering to match XML file order 
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a], 2006-10-03
** fixed bug in install preventing driver installer from running

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31], 2007-08-24
** added Mac OSX (intel) support! - still some minor Qt issues on the mac...
** moved to Q 4.3.0
** 2D and 3D graphing features working
** task pane is hideable and has resizing splitter
** significant improvements to the Subaru ECU defintions thanks to merchgod
** add better visibility options for invalid or higher user level tables
** faster on-demand XML parsing
** add relative directory support in the options
** read only support for H8/539 based mitsubishis - flashing disabled due to lockout problem
** switch to true kwp2000 protocol stack for Subarus
** fix endian reversal in metadata parser - old metadata files are no longer compatible!
** add shbootmode for SH705x processor recovery
** fix asymmetry error in substeps for undo and redo. undo now does steps in exact reverse order, in case two or more substeps operate on the same data (as happens in a 2D interpolation)
** fix crash on editing of static values
** automatically detect and warn if Subarus are not in the test mode when flashing

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]2007-09-06
** removed test mode detection for 2005+ DBW Subarus because some models do not have a test mode connector

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34], 2007-11-05
** fixed crash which occurred when using older OpenPort 1.2 cables
** added automatic notification when new version is released

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35], 2007-05-15
** this is a minor update to support some recent cable changes - a major release is coming soon!
** FTDI drivers updated to CDM 2.02.06
** Qt updated to 4.4.0
** Qwt updated to 5.1.0
** bitfields now supported in bloblists ("blobbits", ie. for periphery bit editing)
** Subaru definitions update to merchgod's 0.8 release 

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* 1.40.2173, 2007-10-21 (??)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178], 2007-10-??
** this release fixes a bug in op20pt32.dll which can allow older firmware to be used if the firmware update fails. using older firmware can lead to flashing failures

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483], 2009-01-29
** EcuFlash Related Changes
*** add support for EVO X CAN reflash
*** add DTC clear option for Evo X
*** add flash recovery mode option and flash recovery mode for Evo X
*** H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03</text>
    <sha1>d79c2cf3ee0c08717b4651b5be9e5896e9c6f495</sha1>
  </revision>
  <revision>
    <id>243</id>
    <parentid>241</parentid>
    <timestamp>2010-11-30T19:57:27Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added 1.24, plus a few 1.41 and 1.43 betas.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12466" xml:space="preserve">[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** First official release
** Command line supports read / flash / compare
** Supports 2001-2005 WRXs
** [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91, 2005-10-25
** This version has been created to support the new OpenPort 1.2. The OpenPort 1.2 has a 12V reflashing voltage that is controlled by RTS line of the virtual serial port which is off by default. EcuFlash now switches this voltage on at the appropriate times.
** This is intended to be the last command line version of EcuFlash. Future versions under development use a GUI and are supported under Windows / OS-X / linux.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2005-11-14
** First GUI version of EcuFlash using the [http://trolltech.com/ Qt Toolkit]
** (We only have the executable, and it might not be the official one at that.)

* 1.21, 2006-04-15
** Add support for drive by wire Subarus (STi,Forrester XT,Legacy GT,Baja,2006+ WRX)
** Switch to 'Mac' styled UI
** Add table view / editing with infinite undo
** Add user definable color maps
** Make 68HC916Y5 (WRX) kernel deal with bad serial data better

* 1.22, 2006-04-16
** Add flipx/flipy to axes widgets
** Change default color map

* 1.23, 2006-04-29
** Fix bug in SH7055 kernel that caused incorrect FMCLR register to be chosen
** Table checkboxes now single click and only hot within checkbox

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup124.exe 1.24], 2006-04-30
** Fix bug causing crash when ROM images are closed out of order

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25], 2006-05-01
** Add user level option to hide obscure tables

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26], 2006-05-10
** This is the first version to officially support Mitsubishi vehicles (Evo 7/8,Eclipse,Lancer). Some ROM definitions are included, more will be added later
** Added driver installer to EcuFlash installation
** Installer backs up your current metadata to 'backupXXX'
** Removed option to delete maps until it works
** Added a needed checksum module for DBW Subarus
** Added support for float and double data types in scalings
** Added idle category
** Improved help in scalings editor
** Adaptive cell sizing in tables
** Map windows have ROM file in the title
** Added procedure steps for connecting to Mitsubishis
** Added directory browsing to options

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27], 2006-05-15
** Some new maps added to Evos
** Improved programming voltage messages for Subaru
** Fixed bug in tracking open map views when metadata view changed
** Expanded table cell sizing a bit to prevent ellipses

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28], 2006-06-20
** Evo 9 reflash support added
** Eclipse AT reflash support added
** Evo 9 map support improved
** Update all Mitsubishi XML definitions to use new reflash tool names
** Improved cell sizing further
** Fix problem of options changing when browsing options menus and canceling
** Add support for hex data entry when editing
** Switch to Qt 4.1.3
** Remove need for C runtime DLLs
** Fix update logic when editing map definitions
** Reset reference ROM data when reading a ROM
** Fix crash on edit of table with no parent

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org 
** Added some Mitsubishi ROM definitions 
** Added auto-selection of OpenPort cables 
** Added descriptive icons to tables in metadata view 
** Fixed bug with tables having 2 generations of parents 
** Fixed bug with incorrect XMLID in new ROM wizard 
** Added ability to load a ROM file from the command line 
** Improved color scaling handling 
** Changed table to show only units for main data 
** Improved table layout 
** Added help text to tables 
** Fix metadata ordering to match XML file order 
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a], 2006-10-03
** fixed bug in install preventing driver installer from running

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31], 2007-08-24
** added Mac OSX (intel) support! - still some minor Qt issues on the mac...
** moved to Q 4.3.0
** 2D and 3D graphing features working
** task pane is hideable and has resizing splitter
** significant improvements to the Subaru ECU defintions thanks to merchgod
** add better visibility options for invalid or higher user level tables
** faster on-demand XML parsing
** add relative directory support in the options
** read only support for H8/539 based mitsubishis - flashing disabled due to lockout problem
** switch to true kwp2000 protocol stack for Subarus
** fix endian reversal in metadata parser - old metadata files are no longer compatible!
** add shbootmode for SH705x processor recovery
** fix asymmetry error in substeps for undo and redo. undo now does steps in exact reverse order, in case two or more substeps operate on the same data (as happens in a 2D interpolation)
** fix crash on editing of static values
** automatically detect and warn if Subarus are not in the test mode when flashing

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]2007-09-06
** removed test mode detection for 2005+ DBW Subarus because some models do not have a test mode connector

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34], 2007-11-05
** fixed crash which occurred when using older OpenPort 1.2 cables
** added automatic notification when new version is released

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35], 2007-05-15
** this is a minor update to support some recent cable changes - a major release is coming soon!
** FTDI drivers updated to CDM 2.02.06
** Qt updated to 4.4.0
** Qwt updated to 5.1.0
** bitfields now supported in bloblists ("blobbits", ie. for periphery bit editing)
** Subaru definitions update to merchgod's 0.8 release 

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* 1.40.2173, 2007-10-21 (??)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178], 2007-10-??
** this release fixes a bug in op20pt32.dll which can allow older firmware to be used if the firmware update fails. using older firmware can lead to flashing failures

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412343_win.exe 1.41.2343], 200?-??-??

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412432_win.exe 1.41.2432], 200?-??-??

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483], 2009-01-29
** EcuFlash Related Changes
*** add support for EVO X CAN reflash
*** add DTC clear option for Evo X
*** add flash recovery mode option and flash recovery mode for Evo X
*** H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000b_win_beta.exe 1.43.3000b] (beta), 2010-05-23

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433095_win_beta.exe 1.43.3095] (beta), 2010-06-10

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150b_win_beta.exe 1.43.3150b] (beta), 2010-09-03

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433172_win_beta.exe 1.43.3172] (beta), 2010-10-12</text>
    <sha1>7661f5d0a7f096ed36fac812b0400d6c3e85d43b</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>MUT Protocol</title>
  <ns>0</ns>
  <id>267</id>
  <revision>
    <id>967</id>
    <timestamp>2010-10-25T02:39:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Quick cut-and-paste; will clean up as a proper protocol spec later.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2031" xml:space="preserve">Quoted from http://www.myrollingroad.com/showthread.php?t=60 CLaNZeR@MyRollingRoad]:

:Okay the Mut Protocol Init is alot like the ISO9141-2 Init.

:We will be using 1 of the Pins from the OBD-II Connector for communicating.

:Pin7 K line

:If you take a Pin HIGH this means you are applying 12Volts to it.
:If you take the Pin LOW you are applying 0V

:The first thing that you need to do is to initialise the ECU so it knows you want to communicate.

:This is done with the following routine:

::'Slow Init
::Take K Line High
::Pause 300ms

::'Send 0x01 (00000001) at rate of 5 baud (LSB) with a Start Bit and a Stop bit

::'Send Startbit
::Set K line low (0)
::Pause 200ms

::'Now to send out 0x01
::'Send out bit0
::Set K line high (1)
::pause 200ms
::'Send out bit1
::Set K line low (0)
::pause 200ms
::'Send out bit2
::Set K line low (0)
::pause 200ms
::'Send out bit3
::Set K line low (0)
::pause 200ms
::'Send out bit4
::Set K line low (0)
::pause 200ms
::'Send out bit5
::Set K line low (0)
::pause 200ms
::'Send out bit6
::Set K line low (0)
::pause 200ms
::'Send out bit7
::Set K line low (0)
::pause 200ms

::'Send Stopbit
::Set K line high (1)
::Pause 200ms

::Switch to 15625 baud

::Receive C0 55 EF 85
::send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second byte of ECU ID
::Send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second Byte of ECU ID
::Send FD
::Receive 20
::Send FD
::Receive 20
::Send FD
::Receive 20

:The ECU is now initialised and you can start sending requests depending on the info you want back.

:For example if you wanted to know the RPM of the engine.

:Send 21 and it will reply with a answer, then simply do a calculation on that result to get the true answer.

:The calculation for RPM is 31.25*x

:Will sort out a list of know Request ID's and their calculations next.

Followup post:

:I have now been informed that after you do the 5 baud Init and then change Baud rate to Receive C0 55 EF 85, you can start sending request bytes straight away.</text>
    <sha1>3a0a5e2766903b2fbf7c1b3af864535208b0abc5</sha1>
  </revision>
  <revision>
    <id>968</id>
    <parentid>967</parentid>
    <timestamp>2010-10-25T15:52:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>More initial information, needs cleanup.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2538" xml:space="preserve">==MUT==

Quoted from http://www.myrollingroad.com/showthread.php?t=60 CLaNZeR@MyRollingRoad]:

:Okay the Mut Protocol Init is alot like the ISO9141-2 Init.

:We will be using 1 of the Pins from the OBD-II Connector for communicating.

:Pin7 K line

:If you take a Pin HIGH this means you are applying 12Volts to it.
:If you take the Pin LOW you are applying 0V

:The first thing that you need to do is to initialise the ECU so it knows you want to communicate.

:This is done with the following routine:

::'Slow Init
::Take K Line High
::Pause 300ms

::'Send 0x01 (00000001) at rate of 5 baud (LSB) with a Start Bit and a Stop bit

::'Send Startbit
::Set K line low (0)
::Pause 200ms

::'Now to send out 0x01
::'Send out bit0
::Set K line high (1)
::pause 200ms
::'Send out bit1
::Set K line low (0)
::pause 200ms
::'Send out bit2
::Set K line low (0)
::pause 200ms
::'Send out bit3
::Set K line low (0)
::pause 200ms
::'Send out bit4
::Set K line low (0)
::pause 200ms
::'Send out bit5
::Set K line low (0)
::pause 200ms
::'Send out bit6
::Set K line low (0)
::pause 200ms
::'Send out bit7
::Set K line low (0)
::pause 200ms

::'Send Stopbit
::Set K line high (1)
::Pause 200ms

::Switch to 15625 baud

::Receive C0 55 EF 85
::send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second byte of ECU ID
::Send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second Byte of ECU ID
::Send FD
::Receive 20
::Send FD
::Receive 20
::Send FD
::Receive 20

:The ECU is now initialised and you can start sending requests depending on the info you want back.

:For example if you wanted to know the RPM of the engine.

:Send 21 and it will reply with a answer, then simply do a calculation on that result to get the true answer.

:The calculation for RPM is 31.25*x

:Will sort out a list of know Request ID's and their calculations next.

Followup post:

:I have now been informed that after you do the 5 baud Init and then change Baud rate to Receive C0 55 EF 85, you can start sending request bytes straight away.

==MUT over OBD-II (Hybrid)==

See [http://forums.evolutionm.net/7422846-post11.html acamus' post] about using ELM-style loggers (in his case, a bluetooth logger:

:Here is little how to
:1. Open COM port of BT key, e.g. COM6 via HyperTerminal or write simple application
:2. Set baudrate to 19200
:3. Send ATSP0&lt;CR&gt;&lt;LF&gt;
:4. Wait for reply OK - (Bus Init..... OK)
:5. Send A0&lt;MUT ID&gt;&lt;CR&gt;&lt;LF&gt; e.g. A032
:6. Parse reply E0 &lt;value&gt; e.g. E0 80, so value is 0x80
:7. Use formula to get the scaled value</text>
    <sha1>d5f431383dea753bd143b9dfc796734e3b1c687b</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>OBD-II Protocol</title>
  <ns>0</ns>
  <id>268</id>
  <revision>
    <id>972</id>
    <parentid>971</parentid>
    <timestamp>2010-10-25T22:04:22Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)  =OBD-II ISO 14230-2 Protocol Specification=  This document describes the OBD-II ISO 142..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9037" xml:space="preserve">(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from 
various public internet sources. I have been successful building an ODB interface with this information, 
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

0-20	Inter byte timing in ECU response
25-50	Time between end of tester request and start of ECU response or between ECU responses
25-5000	Extended mode for "rspPending"
55-5000	Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
5-20	Inter byte time in tester request

==Initialization==

===Fastinit===

 _________       _____        ____        ____ 
          \_____/     \/\/\/\/    \/\/\/\/
  300ms    25ms  25ms  packet     response 

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

 _________ S ___ 2 3 ___ 6 7 ___        ____        ____ 
          \_/0 1\___/4 5\___/P  \/\/\/\/    \/\/\/\/
  300ms  200 400 400 400 400 250 packet     response 

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit:      200ms low
#:; databit 0, 1:    400ms high
#:; databit 2, 3:    400ms low
#:; databit 4, 5:    400ms high
#:; databit 6, 7:    400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below] 
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

 cmd0 cmd1 ... -&gt; result0 result1 ...   comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

 yy 00 -&gt; xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

 01 00 -&gt; xx xx xx xx capabilites 
 01 01 -&gt; [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
 01 03 -&gt; xx xx  Fuel System Status		bitmap 	b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
 01 04 -&gt; xx     Calculated Load Value		%	x*100.0/255	
 01 05 -&gt; xx     Engine Coolant Temperature	C	x-40	
 01 06 -&gt; xx     Short term fuel trim Bank 1	%	x*(100.0/128)-100
 01 07 -&gt; xx     Long  term fuel trim Bank 1	%	x*(100.0/128)-100
 01 08 -&gt;        Short term fuel trim Bank 2	%	x*(100.0/128)-100
 01 09 -&gt;        Long  term fuel trim Bank 2	%	x*(100.0/128)-100
 01 0a -&gt;        Fuel Pressure			kPaG	x*3
 01 0b -&gt; xx     Intake Manifold Pressure	kPaA	x
 01 0c -&gt; xx xx  Engine RPM			RPM	x*0.25
 01 0d -&gt; xx     Vehicle Speed			km/h	x
 01 0e -&gt; xx     Ignition timing advance Cyl #1	deg	X*0.5-64
 01 0f -&gt; xx     Intake Air Temperature		C	X-40
 01 10 -&gt; xx xx  Air Flow Rate			gm/s	X*0.01
 01 11 -&gt; xx     Absolute Throttle Position	%	X*(100.0/255)
 01 12 -&gt; xx     Commanded secondary air status
 01 13 -&gt; xx     Oxygen sensor locations		bitmap	b0=sensor1, b1=sensor2, ..., b7=sensor8
 01 14 -&gt; xx yy  Bank 1 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 15 -&gt; xx yy  Bank 1 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 16 -&gt;        Bank 1 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 17 -&gt;        Bank 1 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 18 -&gt;        Bank 2 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 19 -&gt;        Bank 2 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1a -&gt;        Bank 2 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1b -&gt;        Bank 2 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1c -&gt; xx     Auxiliary Input Status		bitmap	b0:PTO Active
 01 20 -&gt; xx xx xx xx capabilities
 01 21 -&gt; xx xx

 02 00 00 -&gt; xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
 02 02 00 -&gt; [dtc1h] [dtc1l]         DTC that caused freezeframe

 03 -&gt; [dtc1h] [dtc1l] 00 00 00 00

 05 00 00 -&gt; xx xx xx xx capabilites

 06 00 -&gt; xx xx xx xx capabilites
 06 yy -&gt; [max=01,min=81] [valH] [valL] [limitH] [limitL]
 example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
 06 01 -&gt; xx xx xx xx xx   ncms
 06 02 -&gt; xx xx xx xx xx   ncms
 06 09 -&gt; 01 xx xx xx xx -&gt; 81 xx xx xx xx  ncms

 07 -&gt; 00 00 00 00 00 00   cms

 08 00 00 00 00 00 00 -&gt; xx xx xx xx capabilites SMART: none

 09 00 -&gt; 01 30 00 00 00   capabilites  5 bytes??? 

 10	Start Diagnostic Session
 11	ECU Reset
 12	Read Freeze Frame Data
 13	Read Diagnostic Trouble Codes
 14	Clear Diagnostic Information
 17	Read Status Of Diagnostic Trouble Codes
 18	Read Diagnostic Trouble Codes By Status
 1A	Read Ecu Id
 20	Stop Diagnostic Session
 21	Read Data By Local Id
 22	Read Data By Common Id
 23	Read Memory By Address
 25	Stop Repeated Data Transmission
 26	Set Data Rates
 27	Security Access
 2C	Dynamically Define Local Id
 2E	Write Data By Common Id
 2F	Input Output Control By Common Id
 30	Input Output Control By Local Id
 31	Start Routine By Local ID
 32	Stop Routine By Local ID
 33	Request Routine Results By Local Id
 34	Request Download
 35	Request Upload
 36	Transfer data
 37	Request transfer exit
 38	Start Routine By Address
 39	Stop Routine By Address
 3A	Request Routine Results By Address
 3B	Write Data By Local Id
 3D	Write Memory By Address
 3E	Tester Present
 81 -&gt; xx xx	Start Communication
 82	Stop Communication
 83	Access Timing Parameters
 85	Start Programming Mode

===Response Failure Codes===

 10	General Reject
 11	Service Not Supported
 12	Sub Function Not Supported - Invalid Format
 21	Busy - repeat Request
 22	Conditions Not Correct Or Request Sequence Error
 23	Routine Not Complete Or Service In Progress
 31	Request Out Of Range
 33	Security Access Denied - security Access Requested
 35	Invalid Key
 36	Exceed Number Of Attempts
 37	Required Time Delay Not Expired
 40	Download Not Accepted
 41	Improper Download Type
 42	Can Not Download To Specified Address
 43	Can Not Download Number Of Bytes Requested
 50	Upload Not Accepted
 51	Improper Upload Type
 52	Can Not Upload From Specified Address
 53	Can Not Upload Number Of Bytes Requested
 71	Transfer Suspended
 72	Transfer Aborted
 74	Illegal Address In Block Transfer
 75	Illegal Byte Count In Block Transfer
 76	Illegal Block Trasnfer Type
 77	Block Transfer Data Checksum Error
 78	Request Correcty Rcvd - Rsp Pending
 79	Incorrect Byte Count During Block Transfer
 80	Service Not Supported In Active Diagnostic Mode
 C1	Start Comms +ve response
 C2	Stop Comms +ve response
 C3	Access Timing Params +ve response
 81-8F	Reserved
 90-F9	Vehicle manufacturer specific 
 FA-FE	System supplier specific 
 FF	Reserved by document 

==Sample scan obtained of a SMART FOR TWO car==

 --wakeup
 81 -&gt; e9 8f
 --get capabilities
 01 00 -&gt; b2 3f f8 11     capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
 01 20 -&gt; 80 00 00 00     capabilities service 1: 21
 02 00 00 -&gt; 7e 38 00 00  capabilities service 2: 2 3 4 5 6 7 b c d
 05 00 00 -&gt; 7f 05 11     capabilities service 5: none
 06 00 -&gt; ff c0 80 00     capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
 08 00 00 00 00 00 00 -&gt; 7f 08 11    capabilities service 8: none
 09 00 -&gt; 01 30 00 00 00  ???? expected 4 byte response...
 --get status
 01 01 -&gt; 01 07 69 00     MIL light off, 1 dtc, ready, no 02monotoring
 --get dtc's
 03 -&gt; 07 02 00 00 00 00  dtc P0702
 --scan sensors
 01 03
 01 04
 01 05 -&gt; 3a  engine coolant temp = 18C (3a=58 dec - 40 dec)
 01 06
 01 07
 01 0b
 01 0c
 01 0d
 01 0e
 01 0f
 01 10
 01 11
 01 12
 01 13 -&gt; 03   2 sensors
 01 14
 01 15
 01 1c
 01 20 -&gt; 80 00 00 00   (always same: capabilities 21-40)
 01 21 -&gt; 00 37</text>
    <sha1>4f98fea2e06182bb1d33ec056b2fb152c7325d79</sha1>
  </revision>
  <revision>
    <id>969</id>
    <timestamp>2010-11-06T19:05:31Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Timing (in ms) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9042" xml:space="preserve">(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from 
various public internet sources. I have been successful building an ODB interface with this information, 
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

 0-20	Inter byte timing in ECU response
 25-50	Time between end of tester request and start of ECU response or between ECU responses
 25-5000	Extended mode for "rspPending"
 55-5000	Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
 5-20	Inter byte time in tester request

==Initialization==

===Fastinit===

 _________       _____        ____        ____ 
          \_____/     \/\/\/\/    \/\/\/\/
  300ms    25ms  25ms  packet     response 

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

 _________ S ___ 2 3 ___ 6 7 ___        ____        ____ 
          \_/0 1\___/4 5\___/P  \/\/\/\/    \/\/\/\/
  300ms  200 400 400 400 400 250 packet     response 

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit:      200ms low
#:; databit 0, 1:    400ms high
#:; databit 2, 3:    400ms low
#:; databit 4, 5:    400ms high
#:; databit 6, 7:    400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below] 
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

 cmd0 cmd1 ... -&gt; result0 result1 ...   comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

 yy 00 -&gt; xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

 01 00 -&gt; xx xx xx xx capabilites 
 01 01 -&gt; [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
 01 03 -&gt; xx xx  Fuel System Status		bitmap 	b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
 01 04 -&gt; xx     Calculated Load Value		%	x*100.0/255	
 01 05 -&gt; xx     Engine Coolant Temperature	C	x-40	
 01 06 -&gt; xx     Short term fuel trim Bank 1	%	x*(100.0/128)-100
 01 07 -&gt; xx     Long  term fuel trim Bank 1	%	x*(100.0/128)-100
 01 08 -&gt;        Short term fuel trim Bank 2	%	x*(100.0/128)-100
 01 09 -&gt;        Long  term fuel trim Bank 2	%	x*(100.0/128)-100
 01 0a -&gt;        Fuel Pressure			kPaG	x*3
 01 0b -&gt; xx     Intake Manifold Pressure	kPaA	x
 01 0c -&gt; xx xx  Engine RPM			RPM	x*0.25
 01 0d -&gt; xx     Vehicle Speed			km/h	x
 01 0e -&gt; xx     Ignition timing advance Cyl #1	deg	X*0.5-64
 01 0f -&gt; xx     Intake Air Temperature		C	X-40
 01 10 -&gt; xx xx  Air Flow Rate			gm/s	X*0.01
 01 11 -&gt; xx     Absolute Throttle Position	%	X*(100.0/255)
 01 12 -&gt; xx     Commanded secondary air status
 01 13 -&gt; xx     Oxygen sensor locations		bitmap	b0=sensor1, b1=sensor2, ..., b7=sensor8
 01 14 -&gt; xx yy  Bank 1 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 15 -&gt; xx yy  Bank 1 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 16 -&gt;        Bank 1 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 17 -&gt;        Bank 1 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 18 -&gt;        Bank 2 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 19 -&gt;        Bank 2 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1a -&gt;        Bank 2 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1b -&gt;        Bank 2 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1c -&gt; xx     Auxiliary Input Status		bitmap	b0:PTO Active
 01 20 -&gt; xx xx xx xx capabilities
 01 21 -&gt; xx xx

 02 00 00 -&gt; xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
 02 02 00 -&gt; [dtc1h] [dtc1l]         DTC that caused freezeframe

 03 -&gt; [dtc1h] [dtc1l] 00 00 00 00

 05 00 00 -&gt; xx xx xx xx capabilites

 06 00 -&gt; xx xx xx xx capabilites
 06 yy -&gt; [max=01,min=81] [valH] [valL] [limitH] [limitL]
 example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
 06 01 -&gt; xx xx xx xx xx   ncms
 06 02 -&gt; xx xx xx xx xx   ncms
 06 09 -&gt; 01 xx xx xx xx -&gt; 81 xx xx xx xx  ncms

 07 -&gt; 00 00 00 00 00 00   cms

 08 00 00 00 00 00 00 -&gt; xx xx xx xx capabilites SMART: none

 09 00 -&gt; 01 30 00 00 00   capabilites  5 bytes??? 

 10	Start Diagnostic Session
 11	ECU Reset
 12	Read Freeze Frame Data
 13	Read Diagnostic Trouble Codes
 14	Clear Diagnostic Information
 17	Read Status Of Diagnostic Trouble Codes
 18	Read Diagnostic Trouble Codes By Status
 1A	Read Ecu Id
 20	Stop Diagnostic Session
 21	Read Data By Local Id
 22	Read Data By Common Id
 23	Read Memory By Address
 25	Stop Repeated Data Transmission
 26	Set Data Rates
 27	Security Access
 2C	Dynamically Define Local Id
 2E	Write Data By Common Id
 2F	Input Output Control By Common Id
 30	Input Output Control By Local Id
 31	Start Routine By Local ID
 32	Stop Routine By Local ID
 33	Request Routine Results By Local Id
 34	Request Download
 35	Request Upload
 36	Transfer data
 37	Request transfer exit
 38	Start Routine By Address
 39	Stop Routine By Address
 3A	Request Routine Results By Address
 3B	Write Data By Local Id
 3D	Write Memory By Address
 3E	Tester Present
 81 -&gt; xx xx	Start Communication
 82	Stop Communication
 83	Access Timing Parameters
 85	Start Programming Mode

===Response Failure Codes===

 10	General Reject
 11	Service Not Supported
 12	Sub Function Not Supported - Invalid Format
 21	Busy - repeat Request
 22	Conditions Not Correct Or Request Sequence Error
 23	Routine Not Complete Or Service In Progress
 31	Request Out Of Range
 33	Security Access Denied - security Access Requested
 35	Invalid Key
 36	Exceed Number Of Attempts
 37	Required Time Delay Not Expired
 40	Download Not Accepted
 41	Improper Download Type
 42	Can Not Download To Specified Address
 43	Can Not Download Number Of Bytes Requested
 50	Upload Not Accepted
 51	Improper Upload Type
 52	Can Not Upload From Specified Address
 53	Can Not Upload Number Of Bytes Requested
 71	Transfer Suspended
 72	Transfer Aborted
 74	Illegal Address In Block Transfer
 75	Illegal Byte Count In Block Transfer
 76	Illegal Block Trasnfer Type
 77	Block Transfer Data Checksum Error
 78	Request Correcty Rcvd - Rsp Pending
 79	Incorrect Byte Count During Block Transfer
 80	Service Not Supported In Active Diagnostic Mode
 C1	Start Comms +ve response
 C2	Stop Comms +ve response
 C3	Access Timing Params +ve response
 81-8F	Reserved
 90-F9	Vehicle manufacturer specific 
 FA-FE	System supplier specific 
 FF	Reserved by document 

==Sample scan obtained of a SMART FOR TWO car==

 --wakeup
 81 -&gt; e9 8f
 --get capabilities
 01 00 -&gt; b2 3f f8 11     capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
 01 20 -&gt; 80 00 00 00     capabilities service 1: 21
 02 00 00 -&gt; 7e 38 00 00  capabilities service 2: 2 3 4 5 6 7 b c d
 05 00 00 -&gt; 7f 05 11     capabilities service 5: none
 06 00 -&gt; ff c0 80 00     capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
 08 00 00 00 00 00 00 -&gt; 7f 08 11    capabilities service 8: none
 09 00 -&gt; 01 30 00 00 00  ???? expected 4 byte response...
 --get status
 01 01 -&gt; 01 07 69 00     MIL light off, 1 dtc, ready, no 02monotoring
 --get dtc's
 03 -&gt; 07 02 00 00 00 00  dtc P0702
 --scan sensors
 01 03
 01 04
 01 05 -&gt; 3a  engine coolant temp = 18C (3a=58 dec - 40 dec)
 01 06
 01 07
 01 0b
 01 0c
 01 0d
 01 0e
 01 0f
 01 10
 01 11
 01 12
 01 13 -&gt; 03   2 sensors
 01 14
 01 15
 01 1c
 01 20 -&gt; 80 00 00 00   (always same: capabilities 21-40)
 01 21 -&gt; 00 37</text>
    <sha1>a180de9ade95b6da2444f2aac9d6deda90f83ad2</sha1>
  </revision>
  <revision>
    <id>970</id>
    <parentid>969</parentid>
    <timestamp>2010-11-06T19:06:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Timing (in ms) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9057" xml:space="preserve">(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from 
various public internet sources. I have been successful building an ODB interface with this information, 
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

; 0-20 : Inter byte timing in ECU response
; 25-50 : Time between end of tester request and start of ECU response or between ECU responses
; 25-5000 : Extended mode for "rspPending"
; 55-5000 : Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
; 5-20 : Inter byte time in tester request

==Initialization==

===Fastinit===

 _________       _____        ____        ____ 
          \_____/     \/\/\/\/    \/\/\/\/
  300ms    25ms  25ms  packet     response 

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

 _________ S ___ 2 3 ___ 6 7 ___        ____        ____ 
          \_/0 1\___/4 5\___/P  \/\/\/\/    \/\/\/\/
  300ms  200 400 400 400 400 250 packet     response 

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit:      200ms low
#:; databit 0, 1:    400ms high
#:; databit 2, 3:    400ms low
#:; databit 4, 5:    400ms high
#:; databit 6, 7:    400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below] 
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

 cmd0 cmd1 ... -&gt; result0 result1 ...   comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

 yy 00 -&gt; xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

 01 00 -&gt; xx xx xx xx capabilites 
 01 01 -&gt; [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
 01 03 -&gt; xx xx  Fuel System Status		bitmap 	b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
 01 04 -&gt; xx     Calculated Load Value		%	x*100.0/255	
 01 05 -&gt; xx     Engine Coolant Temperature	C	x-40	
 01 06 -&gt; xx     Short term fuel trim Bank 1	%	x*(100.0/128)-100
 01 07 -&gt; xx     Long  term fuel trim Bank 1	%	x*(100.0/128)-100
 01 08 -&gt;        Short term fuel trim Bank 2	%	x*(100.0/128)-100
 01 09 -&gt;        Long  term fuel trim Bank 2	%	x*(100.0/128)-100
 01 0a -&gt;        Fuel Pressure			kPaG	x*3
 01 0b -&gt; xx     Intake Manifold Pressure	kPaA	x
 01 0c -&gt; xx xx  Engine RPM			RPM	x*0.25
 01 0d -&gt; xx     Vehicle Speed			km/h	x
 01 0e -&gt; xx     Ignition timing advance Cyl #1	deg	X*0.5-64
 01 0f -&gt; xx     Intake Air Temperature		C	X-40
 01 10 -&gt; xx xx  Air Flow Rate			gm/s	X*0.01
 01 11 -&gt; xx     Absolute Throttle Position	%	X*(100.0/255)
 01 12 -&gt; xx     Commanded secondary air status
 01 13 -&gt; xx     Oxygen sensor locations		bitmap	b0=sensor1, b1=sensor2, ..., b7=sensor8
 01 14 -&gt; xx yy  Bank 1 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 15 -&gt; xx yy  Bank 1 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 16 -&gt;        Bank 1 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 17 -&gt;        Bank 1 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 18 -&gt;        Bank 2 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 19 -&gt;        Bank 2 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1a -&gt;        Bank 2 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1b -&gt;        Bank 2 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1c -&gt; xx     Auxiliary Input Status		bitmap	b0:PTO Active
 01 20 -&gt; xx xx xx xx capabilities
 01 21 -&gt; xx xx

 02 00 00 -&gt; xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
 02 02 00 -&gt; [dtc1h] [dtc1l]         DTC that caused freezeframe

 03 -&gt; [dtc1h] [dtc1l] 00 00 00 00

 05 00 00 -&gt; xx xx xx xx capabilites

 06 00 -&gt; xx xx xx xx capabilites
 06 yy -&gt; [max=01,min=81] [valH] [valL] [limitH] [limitL]
 example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
 06 01 -&gt; xx xx xx xx xx   ncms
 06 02 -&gt; xx xx xx xx xx   ncms
 06 09 -&gt; 01 xx xx xx xx -&gt; 81 xx xx xx xx  ncms

 07 -&gt; 00 00 00 00 00 00   cms

 08 00 00 00 00 00 00 -&gt; xx xx xx xx capabilites SMART: none

 09 00 -&gt; 01 30 00 00 00   capabilites  5 bytes??? 

 10	Start Diagnostic Session
 11	ECU Reset
 12	Read Freeze Frame Data
 13	Read Diagnostic Trouble Codes
 14	Clear Diagnostic Information
 17	Read Status Of Diagnostic Trouble Codes
 18	Read Diagnostic Trouble Codes By Status
 1A	Read Ecu Id
 20	Stop Diagnostic Session
 21	Read Data By Local Id
 22	Read Data By Common Id
 23	Read Memory By Address
 25	Stop Repeated Data Transmission
 26	Set Data Rates
 27	Security Access
 2C	Dynamically Define Local Id
 2E	Write Data By Common Id
 2F	Input Output Control By Common Id
 30	Input Output Control By Local Id
 31	Start Routine By Local ID
 32	Stop Routine By Local ID
 33	Request Routine Results By Local Id
 34	Request Download
 35	Request Upload
 36	Transfer data
 37	Request transfer exit
 38	Start Routine By Address
 39	Stop Routine By Address
 3A	Request Routine Results By Address
 3B	Write Data By Local Id
 3D	Write Memory By Address
 3E	Tester Present
 81 -&gt; xx xx	Start Communication
 82	Stop Communication
 83	Access Timing Parameters
 85	Start Programming Mode

===Response Failure Codes===

 10	General Reject
 11	Service Not Supported
 12	Sub Function Not Supported - Invalid Format
 21	Busy - repeat Request
 22	Conditions Not Correct Or Request Sequence Error
 23	Routine Not Complete Or Service In Progress
 31	Request Out Of Range
 33	Security Access Denied - security Access Requested
 35	Invalid Key
 36	Exceed Number Of Attempts
 37	Required Time Delay Not Expired
 40	Download Not Accepted
 41	Improper Download Type
 42	Can Not Download To Specified Address
 43	Can Not Download Number Of Bytes Requested
 50	Upload Not Accepted
 51	Improper Upload Type
 52	Can Not Upload From Specified Address
 53	Can Not Upload Number Of Bytes Requested
 71	Transfer Suspended
 72	Transfer Aborted
 74	Illegal Address In Block Transfer
 75	Illegal Byte Count In Block Transfer
 76	Illegal Block Trasnfer Type
 77	Block Transfer Data Checksum Error
 78	Request Correcty Rcvd - Rsp Pending
 79	Incorrect Byte Count During Block Transfer
 80	Service Not Supported In Active Diagnostic Mode
 C1	Start Comms +ve response
 C2	Stop Comms +ve response
 C3	Access Timing Params +ve response
 81-8F	Reserved
 90-F9	Vehicle manufacturer specific 
 FA-FE	System supplier specific 
 FF	Reserved by document 

==Sample scan obtained of a SMART FOR TWO car==

 --wakeup
 81 -&gt; e9 8f
 --get capabilities
 01 00 -&gt; b2 3f f8 11     capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
 01 20 -&gt; 80 00 00 00     capabilities service 1: 21
 02 00 00 -&gt; 7e 38 00 00  capabilities service 2: 2 3 4 5 6 7 b c d
 05 00 00 -&gt; 7f 05 11     capabilities service 5: none
 06 00 -&gt; ff c0 80 00     capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
 08 00 00 00 00 00 00 -&gt; 7f 08 11    capabilities service 8: none
 09 00 -&gt; 01 30 00 00 00  ???? expected 4 byte response...
 --get status
 01 01 -&gt; 01 07 69 00     MIL light off, 1 dtc, ready, no 02monotoring
 --get dtc's
 03 -&gt; 07 02 00 00 00 00  dtc P0702
 --scan sensors
 01 03
 01 04
 01 05 -&gt; 3a  engine coolant temp = 18C (3a=58 dec - 40 dec)
 01 06
 01 07
 01 0b
 01 0c
 01 0d
 01 0e
 01 0f
 01 10
 01 11
 01 12
 01 13 -&gt; 03   2 sensors
 01 14
 01 15
 01 1c
 01 20 -&gt; 80 00 00 00   (always same: capabilities 21-40)
 01 21 -&gt; 00 37</text>
    <sha1>bf41d4bc52353302d8665274e3d03dbc18cf2598</sha1>
  </revision>
  <revision>
    <id>971</id>
    <parentid>970</parentid>
    <timestamp>2010-11-06T19:07:23Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>/* Timing (in ms) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9062" xml:space="preserve">(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from 
various public internet sources. I have been successful building an ODB interface with this information, 
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

:; 0-20 : Inter byte timing in ECU response
:; 25-50 : Time between end of tester request and start of ECU response or between ECU responses
:; 25-5000 : Extended mode for "rspPending"
:; 55-5000 : Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
:; 5-20 : Inter byte time in tester request

==Initialization==

===Fastinit===

 _________       _____        ____        ____ 
          \_____/     \/\/\/\/    \/\/\/\/
  300ms    25ms  25ms  packet     response 

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

 _________ S ___ 2 3 ___ 6 7 ___        ____        ____ 
          \_/0 1\___/4 5\___/P  \/\/\/\/    \/\/\/\/
  300ms  200 400 400 400 400 250 packet     response 

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit:      200ms low
#:; databit 0, 1:    400ms high
#:; databit 2, 3:    400ms low
#:; databit 4, 5:    400ms high
#:; databit 6, 7:    400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66    33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae   01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below] 
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

 cmd0 cmd1 ... -&gt; result0 result1 ...   comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

 yy 00 -&gt; xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

 01 00 -&gt; xx xx xx xx capabilites 
 01 01 -&gt; [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
 01 03 -&gt; xx xx  Fuel System Status		bitmap 	b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
 01 04 -&gt; xx     Calculated Load Value		%	x*100.0/255	
 01 05 -&gt; xx     Engine Coolant Temperature	C	x-40	
 01 06 -&gt; xx     Short term fuel trim Bank 1	%	x*(100.0/128)-100
 01 07 -&gt; xx     Long  term fuel trim Bank 1	%	x*(100.0/128)-100
 01 08 -&gt;        Short term fuel trim Bank 2	%	x*(100.0/128)-100
 01 09 -&gt;        Long  term fuel trim Bank 2	%	x*(100.0/128)-100
 01 0a -&gt;        Fuel Pressure			kPaG	x*3
 01 0b -&gt; xx     Intake Manifold Pressure	kPaA	x
 01 0c -&gt; xx xx  Engine RPM			RPM	x*0.25
 01 0d -&gt; xx     Vehicle Speed			km/h	x
 01 0e -&gt; xx     Ignition timing advance Cyl #1	deg	X*0.5-64
 01 0f -&gt; xx     Intake Air Temperature		C	X-40
 01 10 -&gt; xx xx  Air Flow Rate			gm/s	X*0.01
 01 11 -&gt; xx     Absolute Throttle Position	%	X*(100.0/255)
 01 12 -&gt; xx     Commanded secondary air status
 01 13 -&gt; xx     Oxygen sensor locations		bitmap	b0=sensor1, b1=sensor2, ..., b7=sensor8
 01 14 -&gt; xx yy  Bank 1 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 15 -&gt; xx yy  Bank 1 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 16 -&gt;        Bank 1 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 17 -&gt;        Bank 1 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 18 -&gt;        Bank 2 Sensor 1 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 19 -&gt;        Bank 2 Sensor 2 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1a -&gt;        Bank 2 Sensor 3 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1b -&gt;        Bank 2 Sensor 4 Voltage/Trim	V, %	x*0.005, if y!=ff then y*(100.0/128)-100)
 01 1c -&gt; xx     Auxiliary Input Status		bitmap	b0:PTO Active
 01 20 -&gt; xx xx xx xx capabilities
 01 21 -&gt; xx xx

 02 00 00 -&gt; xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
 02 02 00 -&gt; [dtc1h] [dtc1l]         DTC that caused freezeframe

 03 -&gt; [dtc1h] [dtc1l] 00 00 00 00

 05 00 00 -&gt; xx xx xx xx capabilites

 06 00 -&gt; xx xx xx xx capabilites
 06 yy -&gt; [max=01,min=81] [valH] [valL] [limitH] [limitL]
 example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
 06 01 -&gt; xx xx xx xx xx   ncms
 06 02 -&gt; xx xx xx xx xx   ncms
 06 09 -&gt; 01 xx xx xx xx -&gt; 81 xx xx xx xx  ncms

 07 -&gt; 00 00 00 00 00 00   cms

 08 00 00 00 00 00 00 -&gt; xx xx xx xx capabilites SMART: none

 09 00 -&gt; 01 30 00 00 00   capabilites  5 bytes??? 

 10	Start Diagnostic Session
 11	ECU Reset
 12	Read Freeze Frame Data
 13	Read Diagnostic Trouble Codes
 14	Clear Diagnostic Information
 17	Read Status Of Diagnostic Trouble Codes
 18	Read Diagnostic Trouble Codes By Status
 1A	Read Ecu Id
 20	Stop Diagnostic Session
 21	Read Data By Local Id
 22	Read Data By Common Id
 23	Read Memory By Address
 25	Stop Repeated Data Transmission
 26	Set Data Rates
 27	Security Access
 2C	Dynamically Define Local Id
 2E	Write Data By Common Id
 2F	Input Output Control By Common Id
 30	Input Output Control By Local Id
 31	Start Routine By Local ID
 32	Stop Routine By Local ID
 33	Request Routine Results By Local Id
 34	Request Download
 35	Request Upload
 36	Transfer data
 37	Request transfer exit
 38	Start Routine By Address
 39	Stop Routine By Address
 3A	Request Routine Results By Address
 3B	Write Data By Local Id
 3D	Write Memory By Address
 3E	Tester Present
 81 -&gt; xx xx	Start Communication
 82	Stop Communication
 83	Access Timing Parameters
 85	Start Programming Mode

===Response Failure Codes===

 10	General Reject
 11	Service Not Supported
 12	Sub Function Not Supported - Invalid Format
 21	Busy - repeat Request
 22	Conditions Not Correct Or Request Sequence Error
 23	Routine Not Complete Or Service In Progress
 31	Request Out Of Range
 33	Security Access Denied - security Access Requested
 35	Invalid Key
 36	Exceed Number Of Attempts
 37	Required Time Delay Not Expired
 40	Download Not Accepted
 41	Improper Download Type
 42	Can Not Download To Specified Address
 43	Can Not Download Number Of Bytes Requested
 50	Upload Not Accepted
 51	Improper Upload Type
 52	Can Not Upload From Specified Address
 53	Can Not Upload Number Of Bytes Requested
 71	Transfer Suspended
 72	Transfer Aborted
 74	Illegal Address In Block Transfer
 75	Illegal Byte Count In Block Transfer
 76	Illegal Block Trasnfer Type
 77	Block Transfer Data Checksum Error
 78	Request Correcty Rcvd - Rsp Pending
 79	Incorrect Byte Count During Block Transfer
 80	Service Not Supported In Active Diagnostic Mode
 C1	Start Comms +ve response
 C2	Stop Comms +ve response
 C3	Access Timing Params +ve response
 81-8F	Reserved
 90-F9	Vehicle manufacturer specific 
 FA-FE	System supplier specific 
 FF	Reserved by document 

==Sample scan obtained of a SMART FOR TWO car==

 --wakeup
 81 -&gt; e9 8f
 --get capabilities
 01 00 -&gt; b2 3f f8 11     capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
 01 20 -&gt; 80 00 00 00     capabilities service 1: 21
 02 00 00 -&gt; 7e 38 00 00  capabilities service 2: 2 3 4 5 6 7 b c d
 05 00 00 -&gt; 7f 05 11     capabilities service 5: none
 06 00 -&gt; ff c0 80 00     capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
 08 00 00 00 00 00 00 -&gt; 7f 08 11    capabilities service 8: none
 09 00 -&gt; 01 30 00 00 00  ???? expected 4 byte response...
 --get status
 01 01 -&gt; 01 07 69 00     MIL light off, 1 dtc, ready, no 02monotoring
 --get dtc's
 03 -&gt; 07 02 00 00 00 00  dtc P0702
 --scan sensors
 01 03
 01 04
 01 05 -&gt; 3a  engine coolant temp = 18C (3a=58 dec - 40 dec)
 01 06
 01 07
 01 0b
 01 0c
 01 0d
 01 0e
 01 0f
 01 10
 01 11
 01 12
 01 13 -&gt; 03   2 sensors
 01 14
 01 15
 01 1c
 01 20 -&gt; 80 00 00 00   (always same: capabilities 21-40)
 01 21 -&gt; 00 37</text>
    <sha1>9b8cbe0b3908e3cf3fd27864e6848eda409d2dc9</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Locating Tables</title>
  <ns>0</ns>
  <id>269</id>
  <revision>
    <id>973</id>
    <timestamp>2010-11-02T21:57:19Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Added; copied from my post on EvoM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5822" xml:space="preserve">This guide is adapted from [http://forums.evolutionm.net/ecuflash/448378-dev-disassembly-beginners-guide-evo-ecu-table-lookups.html the original thread on EvoM]:

==The beginners' guide to Evo ECU table lookups==

EcuFlash provides an XML file for each ROM, which defines a bunch of tables (1D, 2D, and 3D) that can be edited by the user. Every 2D or 3D table is indexed by one or two "axis" values; it's how you look up values in the table. By way of example, the High Octane Fuel Map has both RPM and Load axes; to look up a value in the table, you first look up the current engine speed (RPM) and calculated load, and the AFR target value you're looking for is where the two intersect on the table. (2D works the same way, but there's only one dimension to worry about.)

The XML tells you where in the ROM the table and axis table data is located. Back to our example, the High Octane Fuel Map table in 96530006 is listed as being at address "33bd", with the "Engine Load" axis as being at address "68b0" and the RPM axis at address "6888". If you pull those up in IDA Pro, you'll see the data listed there, just as EcuFlash promised, but that's not the whole story; if you've ever done this, you'll notice that IDA doesn't have any code or data references listed for those ROM addresses. Every table, and every "axis table", has a header attached to it, just before the data an end-user of EcuFlash normally edits. That header data is used by a set of standard routines that every Evo ROM provides to assist in performing lookups, and the address of that header is what IDA ends up generating code and data references to.

By understanding how the ECU performs lookups in tables, it can help you to both understand when you're looking at code that performs table lookups (thus helping you locate new tables), and help you understand why you get back the values you do when the ECU performs a table lookup.

To get to the value in a table, you have to first look up the axis positions. The axis table header, just prior to the data itself, defines an address to store lookup results in, followed by the address of "current value" of that axis. For example, if the table axis is "RPM", second address is where the current vehicle RPM is stored in memory. The next word defines the number of elements in the axis, and then the axis data follows.

So, axis tables look like this:
* A long word for the result address.
* A long word for the value to look up.
* A word for the length of the axis.
* A series of words, as long as the length, containing the axis data.

Axis lookup is done by calling the routine at &lt;tt&gt;sub_CC6&lt;/tt&gt;. You tell &lt;tt&gt;sub_CC6&lt;/tt&gt; where the axis header is by assigning its address to &lt;tt&gt;r4&lt;/tt&gt;.

For 2D tables, you perform one axis lookup; for 3D tables, you perform two. The result of each call to &lt;tt&gt;sub_CC6&lt;/tt&gt; is a value stored in that axis' "result address"; it's the position in the axis that most closely (rounding down) matches the current value of the axis (ie. the position on an RPM axis that most closely matches the current engine speed).

Once you have the axis positions back from &lt;tt&gt;sub_CC6&lt;/tt&gt;, you need to look up the actual table value. For byte-width tables, you call &lt;tt&gt;sub_C28&lt;/tt&gt;; for word-width tables, &lt;tt&gt;sub_E02&lt;/tt&gt;.

The table header has some similarities to the axis header. The first byte (or word, for &lt;tt&gt;sub_E02&lt;/tt&gt;) determines whether the table has two dimensions (0x2) or three (0x3). The second byte (or word) is a global "adder" that is added to any value returned from the table. Next, a long word describes where the position on the X-axis is stored in memory (returned from &lt;tt&gt;sub_CC6&lt;/tt&gt;); in a 3D table, an additional long word is included, as well as a one-byte value denoting the length of a row. After that, the table data follows, either in word (for &lt;tt&gt;sub_E02&lt;/tt&gt;) or byte (&lt;tt&gt;sub_C28&lt;/tt&gt;) form.

So, tables look like this:
* A byte (or word, for word-sized tables) for the number of dimensions: 2 = 2D, 3 = 3D.
* A byte (or word, for word-sized tables) for a value "added" to all values returned from the table.
* A long word for the position on the X-axis.
* Optionally, a long word for the position on the Y-axis in a 3D table.
* Optionally, a byte (or word, for word-sized tables) for the length of each row in a 3D table.
* A series of words or bytes containing the table data.

Note that the X and Y position addresses must either match the result addresses from the axis tables, or match a pair of addresses that you have manually copied the axis lookup results into.

Just like with axis lookups, you set &lt;tt&gt;r4&lt;/tt&gt; to the address of the table you want to perform the look-up in. When control is returned, &lt;tt&gt;r0&lt;/tt&gt; contains an interpolated value based on how "close" the axis values were to a labelled position on the axis.

So, if you see calls to &lt;tt&gt;sub_CC6&lt;/tt&gt; when reading through your disassembly of a ROM, it's an indication that an axis lookup is being performed, and if you see calls to &lt;tt&gt;sub_C28&lt;/tt&gt; or &lt;tt&gt;sub_E02&lt;/tt&gt;, there's a table lookup happening. Looking at the lines of code leading up to that for any assignments to register &lt;tt&gt;r4&lt;/tt&gt; will tell you where the axis or table headers are located. Normally, the code right after a call to &lt;tt&gt;sub_C28&lt;/tt&gt; or &lt;tt&gt;sub_E02&lt;/tt&gt; will assign &lt;tt&gt;r0&lt;/tt&gt; to some memory address (or eventually get there, by bouncing it around from register to register), which you can log via the MUT table if you want to keep an eye on the value, and can give you an idea of what other code that uses that value is doing (for example, code that deals with the result from a High Octane Fuel Map lookup is probably involved in fueling).

Hopefully, this can help some newer folks get started with understanding one of the most common activities ECU code participates in.</text>
    <sha1>5afb1a49bdca39a4d342175443ded044dcb40864</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>Development Tips</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>680</id>
    <parentid>678</parentid>
    <timestamp>2010-12-27T01:43:06Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Fix a few URLs.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3903" xml:space="preserve">This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called &lt;tt&gt;sh-elf-objdump&lt;/tt&gt;, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://dev.logic.net/hg/esm/file/tip/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a &lt;tt&gt;.ASM&lt;/tt&gt; file that GNU &lt;tt&gt;as&lt;/tt&gt; can use, once you run it through &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;.
;pcrel_filter.sh
:http://dev.logic.net/hg/esm/file/tip/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable &lt;tt&gt;.ASM&lt;/tt&gt; output from &lt;tt&gt;pcrel_filter.sh&lt;/tt&gt;, simply running &lt;tt&gt;sh-elf-as -o rom.o (filename.asm)&lt;/tt&gt; (where &lt;tt&gt;(filename.asm)&lt;/tt&gt; is your produced assembly output) will create a file named &lt;tt&gt;rom.o&lt;/tt&gt;.

Then, run the linker: &lt;tt&gt;sh-elf-ld -o rom rom.o&lt;/tt&gt;.

Finally, you'll need to use a command like &lt;tt&gt;dd if=rom of=rom.hex bs=1 skip=132 count=262144&lt;/tt&gt; to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command &lt;tt&gt;cmp rom.hex (original ROM image)&lt;/tt&gt;, where &lt;tt&gt;(original ROM image)&lt;/tt&gt; is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are &lt;tt&gt;hexdump&lt;/tt&gt; (a flexible program for displaying binary data in a more useful format) and &lt;tt&gt;hexedit&lt;/tt&gt; (a binary file editor).

----

For looking up additional information about the platform used in the Evo ECUs, both the Evo VIII and IX processors are based on SH-2, with the IX processor being a SH-2E variant; specifically, VIIIs use the SH7052F platform, and IXs use SH7055F. The primary difference is that the Evo VIII ECU (SH7052F) has a 256KB ROM image and 12KB of RAM, while the IX ECU (SH7055F) has a 512KB ROM image and 32KB of RAM; otherwise, the hardware is essentially the same.

; SH-2 Software Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

; SH7052F Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/e602185_sh7052f.pdf

; SH7055SF Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0045_sh7055s.pdf

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.</text>
    <sha1>086baebf15bc0b34e1962845c7853bfb64da3e5a</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>User:EdwardMarshall</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>57</id>
    <timestamp>2011-02-16T15:44:11Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="68" xml:space="preserve">I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.</text>
    <sha1>bc8db272730a753bdbbfd1fa7a5502c8822b9c5d</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>89280002</title>
  <ns>0</ns>
  <id>197</id>
  <revision>
    <id>764</id>
    <timestamp>2011-05-09T14:17:29Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add MUT table.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="443" xml:space="preserve">==Information==
Car:  Mitsubisshi Lancer Evolution 9

Year: 2005

Market:

Case id: 

==Replacements==

==Download files==
[[Image:89280002_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:&lt;tt&gt;35920&lt;/tt&gt;

;2-byte load
:&lt;tt&gt;MUT00&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT01&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte RPM
:&lt;tt&gt;MUT02&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT03&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

;2-byte AirFlow
:&lt;tt&gt;MUT04&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;
:&lt;tt&gt;MUT05&lt;/tt&gt; = &lt;tt&gt;&lt;/tt&gt;

[[Category:ROMs|89280002]]</text>
    <sha1>2c7456108dce90337c8a565f774414a5cac1bf50</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>MediaWiki:Common.js</title>
  <ns>8</ns>
  <id>273</id>
  <revision>
    <id>978</id>
    <parentid>977</parentid>
    <timestamp>2012-01-18T06:22:48Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Add SOPA blackout code.</comment>
    <model>javascript</model>
    <format>text/javascript</format>
    <text bytes="299" xml:space="preserve">var rightNow = new Date;
var intlHours = rightNow.getUTCHours();
if( 0 == rightNow.getUTCMonth() &amp;&amp;
    2012 == rightNow.getUTCFullYear() &amp;&amp;
    ((18 == rightNow.getUTCDate() &amp;&amp; 13 &lt;= intlHours) || (19 == rightNow.getUTCDate() &amp;&amp; 0 &gt;= intlHours)))
  window.location = "http://sopastrike.com/strike";</text>
    <sha1>827086ee3ff1bbc03717d7f8aa8ae154aaa4b25a</sha1>
  </revision>
  <revision>
    <id>977</id>
    <timestamp>2012-01-19T23:28:55Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Blanked the page</comment>
    <model>javascript</model>
    <format>text/javascript</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>File:96530006-mod510-new tables.zip</title>
  <ns>6</ns>
  <id>145</id>
  <revision>
    <id>979</id>
    <parentid>621</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96530006-mod510-new tables.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="77" xml:space="preserve">Definition file for 96530006 with tephra mod 5.10 and some newly found tables</text>
    <sha1>31e8d351cef64395760887b6b50d49e6cff40688</sha1>
  </revision>
</page>
<page arvcontinue="20100503213553|914">
  <title>File:96420011 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>202</id>
  <revision>
    <id>980</id>
    <parentid>771</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96420011 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:BoostDelayTimerMap.gif</title>
  <ns>6</ns>
  <id>121</id>
  <revision>
    <id>981</id>
    <parentid>524</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostDelayTimerMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:EcuFlashButtons.gif</title>
  <ns>6</ns>
  <id>112</id>
  <revision>
    <id>982</id>
    <parentid>515</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:EcuFlashButtons.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:88590015-v5.10-JDM MAP.zip</title>
  <ns>6</ns>
  <id>133</id>
  <revision>
    <id>983</id>
    <parentid>563</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88590015-v5.10-JDM MAP.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="118" xml:space="preserve">88590015 Rom file, Rom definition, Rom base definition. Preloaded with Tephra v5.10, mrfreds definitions, and JDM MAP.</text>
    <sha1>02b89123c8258369b1f3dd0b755386c6685bec86</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:88590015.zip</title>
  <ns>6</ns>
  <id>228</id>
  <revision>
    <id>984</id>
    <parentid>834</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88590015.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="51" xml:space="preserve">Stock 88590015 ROM, from http://www.osecuroms.org/.</text>
    <sha1>0a5eaa7103ca05f755835d34531d872c486fcab1</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:RevLimitMap.gif</title>
  <ns>6</ns>
  <id>116</id>
  <revision>
    <id>985</id>
    <parentid>519</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:RevLimitMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:96530706v7t6-LiveMap.zip</title>
  <ns>6</ns>
  <id>223</id>
  <revision>
    <id>986</id>
    <parentid>827</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96530706v7t6-LiveMap.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:80700010 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>172</id>
  <revision>
    <id>987</id>
    <parentid>705</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:80700010 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:ADC-evo8-harness.jpg</title>
  <ns>6</ns>
  <id>246</id>
  <revision>
    <id>988</id>
    <parentid>930</parentid>
    <timestamp>2016-01-11T00:11:24Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:ADC-evo8-harness.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42" xml:space="preserve">[[Map switching harness]] for the Evo VIII</text>
    <sha1>fc2963ff144b12d6391f5a750995a4fd19b990cc</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Openport13.pdf</title>
  <ns>6</ns>
  <id>245</id>
  <revision>
    <id>989</id>
    <parentid>929</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Openport13.pdf]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54" xml:space="preserve">Schematic for the OpenPort 1.3 USB&lt;-&gt;OBD-II interface.</text>
    <sha1>902117c6d8ee5c55f4a75032ebca52b93a72d8b3</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Screen02.gif</title>
  <ns>6</ns>
  <id>113</id>
  <revision>
    <id>990</id>
    <parentid>516</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Screen02.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:94170015.zip</title>
  <ns>6</ns>
  <id>78</id>
  <revision>
    <id>991</id>
    <parentid>267</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170015.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Def file 96530006 tephra510 new tables.zip</title>
  <ns>6</ns>
  <id>148</id>
  <revision>
    <id>992</id>
    <parentid>626</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Def file 96530006 tephra510 new tables.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">XML definition for 96530006.</text>
    <sha1>7e882d80ae632b39857b6c4bb6c792a8e891b535</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Mut-table2.gif</title>
  <ns>6</ns>
  <id>142</id>
  <revision>
    <id>993</id>
    <parentid>616</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Mut-table2.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">Mut table in Ecuflash 1.3</text>
    <sha1>776ff1def556f9aecc456ae54b92062bead972f4</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:3dTableExplained.jpg</title>
  <ns>6</ns>
  <id>120</id>
  <revision>
    <id>994</id>
    <parentid>523</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:3dTableExplained.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:BoostLimitMap.gif</title>
  <ns>6</ns>
  <id>125</id>
  <revision>
    <id>995</id>
    <parentid>528</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostLimitMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:99270000 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>176</id>
  <revision>
    <id>996</id>
    <parentid>709</parentid>
    <timestamp>2016-01-11T00:11:25Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:99270000 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:95960000.zip</title>
  <ns>6</ns>
  <id>224</id>
  <revision>
    <id>997</id>
    <parentid>828</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:95960000.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">95960000 ROM</text>
    <sha1>c0d75e6537d5884e22d900c7920fd8817f13783b</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Warning.gif</title>
  <ns>6</ns>
  <id>260</id>
  <revision>
    <id>998</id>
    <parentid>955</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Warning.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:FuelCurve.gif</title>
  <ns>6</ns>
  <id>127</id>
  <revision>
    <id>999</id>
    <parentid>530</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:FuelCurve.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Nlts-settings.png</title>
  <ns>6</ns>
  <id>105</id>
  <revision>
    <id>1000</id>
    <parentid>447</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Nlts-settings.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">TephraMod V5.9 NLTS Settings</text>
    <sha1>8a99c3cc07ac30ab00d4d77627127308be122e05</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Editing.jpg</title>
  <ns>6</ns>
  <id>86</id>
  <revision>
    <id>1001</id>
    <parentid>305</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Editing.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">Editing the ROM</text>
    <sha1>f295e0274b16bd0be68d82a0f68dd6b1870a206e</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Metatables.jpg</title>
  <ns>6</ns>
  <id>90</id>
  <revision>
    <id>1002</id>
    <parentid>309</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Metatables.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Basic tuning tables</text>
    <sha1>15635818b73b4d2e32416dcf0f08198b9baf20c5</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Ics-settings.PNG</title>
  <ns>6</ns>
  <id>106</id>
  <revision>
    <id>1003</id>
    <parentid>448</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Ics-settings.PNG]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">Intercooler Spray Settings</text>
    <sha1>9142f4ec05c48951c8b07d6d5881638616ea550d</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:92460000 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>200</id>
  <revision>
    <id>1004</id>
    <parentid>769</parentid>
    <timestamp>2016-01-11T00:11:26Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:92460000 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:FuelMap.gif</title>
  <ns>6</ns>
  <id>118</id>
  <revision>
    <id>1005</id>
    <parentid>521</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:FuelMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Limits.jpg</title>
  <ns>6</ns>
  <id>89</id>
  <revision>
    <id>1006</id>
    <parentid>308</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Limits.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Various limit tables</text>
    <sha1>28093e7658dfeb2669fb0f1ff4104e7fdeaddd29</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:98650014 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>204</id>
  <revision>
    <id>1007</id>
    <parentid>773</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:98650014 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:BCS deactivation RPM.JPG</title>
  <ns>6</ns>
  <id>140</id>
  <revision>
    <id>1008</id>
    <parentid>612</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BCS deactivation RPM.JPG]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:EVOSCAN TephraMOD-88590715 ALT.zip</title>
  <ns>6</ns>
  <id>257</id>
  <revision>
    <id>1009</id>
    <parentid>952</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:EVOSCAN TephraMOD-88590715 ALT.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="72" xml:space="preserve">EvoScan XML Definition that will work with TephraMod V7 for Map Tracing.</text>
    <sha1>745622db072fb2bc527c53724e26644a49721115</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:94170715-V7.hex</title>
  <ns>6</ns>
  <id>252</id>
  <revision>
    <id>1010</id>
    <parentid>943</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170715-V7.hex]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="52" xml:space="preserve">94170015 Tephra mods v7. 2 byte MUT changes applied.</text>
    <sha1>6205431d7fc0f69bf97a4850b3e86ccdb8e787d9</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:97250001 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>174</id>
  <revision>
    <id>1011</id>
    <parentid>707</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:97250001 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Save.jpg</title>
  <ns>6</ns>
  <id>93</id>
  <revision>
    <id>1012</id>
    <parentid>312</parentid>
    <timestamp>2016-01-11T00:11:27Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Save.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">how to save a file</text>
    <sha1>02475c9128b2c60c030f8e3144cf53a2408904c6</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:96940011.HEX</title>
  <ns>6</ns>
  <id>3</id>
  <revision>
    <id>1013</id>
    <parentid>61</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96940011.HEX]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47" xml:space="preserve">USDM 2005 Mitsubishi Lancer Evolution ROM image</text>
    <sha1>f3ce035a42b68be1c348eb89383d5551bb04d5e3</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:90160003.hex</title>
  <ns>6</ns>
  <id>231</id>
  <revision>
    <id>1014</id>
    <parentid>843</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:90160003.hex]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55" xml:space="preserve">90160003 ROM from a 2002 Mitsubishi Mirage LS 1.8 4g93.</text>
    <sha1>acf2590386124bfc206f5dd12fe445fac76a88dd</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:96530706v7t6-livemap-sd.zip</title>
  <ns>6</ns>
  <id>222</id>
  <revision>
    <id>1015</id>
    <parentid>826</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96530706v7t6-livemap-sd.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="173" xml:space="preserve">This is the LiveMap app configured for 96530706 v7t6.  It still has some hard coded values and the data tab is setup for the variables that I am logging in my RAM MUT table.</text>
    <sha1>0e15f339bdc71490615cda8b4ce23c84c0bf57c7</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:ADC-evo9-harness.png</title>
  <ns>6</ns>
  <id>247</id>
  <revision>
    <id>1016</id>
    <parentid>931</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:ADC-evo9-harness.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">[[Map switching harness]] for the Evo IX.</text>
    <sha1>f7210123c0d8956021bb10bbc53eef3790ea7eb0</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:96420008.zip</title>
  <ns>6</ns>
  <id>226</id>
  <revision>
    <id>1017</id>
    <parentid>832</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96420008.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">96420008 Stock ROM</text>
    <sha1>c1964e0daf16af50f4ed2350c25c8239e44292aa</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:93660005 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>170</id>
  <revision>
    <id>1018</id>
    <parentid>702</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:93660005 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Indexed.jpg</title>
  <ns>6</ns>
  <id>88</id>
  <revision>
    <id>1019</id>
    <parentid>307</parentid>
    <timestamp>2016-01-11T00:11:28Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Indexed.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">Showing ROM load values in terms of boost</text>
    <sha1>fe9106c0307f8f42b3f30ed0358190dcc5b6e186</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:MaptracerExample.JPG</title>
  <ns>6</ns>
  <id>258</id>
  <revision>
    <id>1020</id>
    <parentid>953</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:MaptracerExample.JPG]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">An example image of the Map tracer with Big Maps</text>
    <sha1>5686d9bdda999d582e2ee6b70bc4dadf879cf777</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:94170014 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>201</id>
  <revision>
    <id>1021</id>
    <parentid>770</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170014 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Headbang2.gif</title>
  <ns>6</ns>
  <id>110</id>
  <revision>
    <id>1022</id>
    <parentid>513</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Headbang2.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Openport12.pdf</title>
  <ns>6</ns>
  <id>251</id>
  <revision>
    <id>1023</id>
    <parentid>941</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Openport12.pdf]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">OpenPort schematic, version 1.2.</text>
    <sha1>9fd5f5c6726e789e4e9d4e7fb4b14ff50e6ee27b</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:88580013 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>199</id>
  <revision>
    <id>1024</id>
    <parentid>768</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88580013 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:88840013 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>185</id>
  <revision>
    <id>1025</id>
    <parentid>740</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88840013 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:96260009 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>186</id>
  <revision>
    <id>1026</id>
    <parentid>741</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96260009 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:3dMap.gif</title>
  <ns>6</ns>
  <id>119</id>
  <revision>
    <id>1027</id>
    <parentid>522</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:3dMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:98650012 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>175</id>
  <revision>
    <id>1028</id>
    <parentid>708</parentid>
    <timestamp>2016-01-11T00:11:29Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:98650012 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:89280002 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>196</id>
  <revision>
    <id>1029</id>
    <parentid>763</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:89280002 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001124|981">
  <title>File:Diag-connector.png</title>
  <ns>6</ns>
  <id>243</id>
  <revision>
    <id>1030</id>
    <parentid>926</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Diag-connector.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">Diagnostic connector from the factory service manual.</text>
    <sha1>1cbb5786de657731c5afbb857a681fd5f8c151d8</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:94170015 w v5.10 MODS.zip</title>
  <ns>6</ns>
  <id>214</id>
  <revision>
    <id>1031</id>
    <parentid>795</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170015 w v5.10 MODS.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">94170015 USDM 8 with all the bells and whistles. Also includes evo7base with all updates.

Both are organized by category "type" to group like items for easier referencing.</text>
    <sha1>525ebe020fa66bbe254240cf116edcf83d15f8be</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:98640014 EVO7 STOCK.zip</title>
  <ns>6</ns>
  <id>164</id>
  <revision>
    <id>1032</id>
    <parentid>695</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:98640014 EVO7 STOCK.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88580014 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>192</id>
  <revision>
    <id>1033</id>
    <parentid>754</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88580014 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88840016 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>188</id>
  <revision>
    <id>1034</id>
    <parentid>747</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88840016 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:2byteto1byte flip.png</title>
  <ns>6</ns>
  <id>220</id>
  <revision>
    <id>1035</id>
    <parentid>823</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:2byteto1byte flip.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="66" xml:space="preserve">Shows what happens when a byte gets flipped during 2 byte logging.</text>
    <sha1>42a7ace61583aa5071f247b8aab0cf41719094f7</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:89960000 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>194</id>
  <revision>
    <id>1036</id>
    <parentid>757</parentid>
    <timestamp>2016-01-11T00:11:30Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:89960000 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Smilie thumbsup.gif</title>
  <ns>6</ns>
  <id>108</id>
  <revision>
    <id>1037</id>
    <parentid>511</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Smilie thumbsup.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:1g aldl schematic simple.jpg</title>
  <ns>6</ns>
  <id>254</id>
  <revision>
    <id>1038</id>
    <parentid>949</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:1g aldl schematic simple.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="59" xml:space="preserve">Simple cable schematic for a 1g DSM ALDL datalogging cable.</text>
    <sha1>74e97ac683604e6d3ed581ad0edb6a4fa672fa21</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:EVO7GTA-OEM-JDM 512k.hex</title>
  <ns>6</ns>
  <id>215</id>
  <revision>
    <id>1039</id>
    <parentid>796</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:EVO7GTA-OEM-JDM 512k.hex]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88570008 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>198</id>
  <revision>
    <id>1040</id>
    <parentid>767</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88570008 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Openport.pdf</title>
  <ns>6</ns>
  <id>250</id>
  <revision>
    <id>1041</id>
    <parentid>940</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Openport.pdf]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">OpenPort original design.</text>
    <sha1>1cb7c38831a90fead5c3bbc06e22e452df329e08</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:BoostErrorMap.gif</title>
  <ns>6</ns>
  <id>117</id>
  <revision>
    <id>1042</id>
    <parentid>520</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostErrorMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Fuel path.jpg</title>
  <ns>6</ns>
  <id>87</id>
  <revision>
    <id>1043</id>
    <parentid>306</parentid>
    <timestamp>2016-01-11T00:11:31Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Fuel path.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">Tracking the ECU's path through the fuel map</text>
    <sha1>6e9a6c695bdb140e7976f5621e87c432c0f0d4cd</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Dual fuel maps.jpg</title>
  <ns>6</ns>
  <id>85</id>
  <revision>
    <id>1044</id>
    <parentid>304</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Dual fuel maps.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Fuel Maps</text>
    <sha1>4c8f836fbd43dd2fc18e66a755f0963064ce6fa5</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Def file 96530006+tephra510+new tables.zip</title>
  <ns>6</ns>
  <id>144</id>
  <revision>
    <id>1045</id>
    <parentid>619</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Def file 96530006+tephra510+new tables.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">Def file 96530006+tephra510+new tables</text>
    <sha1>6701dc24c7f968d1274434e07fa2b8fef0999f35</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:94170015.hex</title>
  <ns>6</ns>
  <id>77</id>
  <revision>
    <id>1046</id>
    <parentid>266</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170015.hex]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Timing maps.jpg</title>
  <ns>6</ns>
  <id>94</id>
  <revision>
    <id>1047</id>
    <parentid>313</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Timing maps.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11" xml:space="preserve">timing maps</text>
    <sha1>5a35dbea8f985b34e766f2f00efc651f79bcbdd5</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:BoostOffsetMap.gif</title>
  <ns>6</ns>
  <id>122</id>
  <revision>
    <id>1048</id>
    <parentid>525</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostOffsetMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:MaxWGDCMap.gif</title>
  <ns>6</ns>
  <id>124</id>
  <revision>
    <id>1049</id>
    <parentid>527</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:MaxWGDCMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:22580006 EVO5 Stock.zip</title>
  <ns>6</ns>
  <id>168</id>
  <revision>
    <id>1050</id>
    <parentid>699</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:22580006 EVO5 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88580015.zip</title>
  <ns>6</ns>
  <id>235</id>
  <revision>
    <id>1051</id>
    <parentid>848</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88580015.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">88580015 ROM.</text>
    <sha1>3af7dea52670c7dbc6a0081a7856061f6ffd26fe</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88590015-v5.10-Direct Boost Ctl.zip</title>
  <ns>6</ns>
  <id>134</id>
  <revision>
    <id>1052</id>
    <parentid>566</parentid>
    <timestamp>2016-01-11T00:11:32Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88590015-v5.10-Direct Boost Ctl.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="140" xml:space="preserve">88590015 Rom file, Rom definition, Rom base definition. Preloaded with Tephra v5.10, mrfreds definitions, JDM MAP, and Direct Boost Control.</text>
    <sha1>7a58e81c22e49b6f46ad4cdb4484a8932587b7b6</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Mut-table.png</title>
  <ns>6</ns>
  <id>72</id>
  <revision>
    <id>1053</id>
    <parentid>260</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Mut-table.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">EcuFlash representation of the Evo MUT table</text>
    <sha1>e13255e33bc96cc4474900a39faccfbbce5a7816</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:BoostDesiredMap.gif</title>
  <ns>6</ns>
  <id>123</id>
  <revision>
    <id>1054</id>
    <parentid>526</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostDesiredMap.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Notepad.gif</title>
  <ns>6</ns>
  <id>261</id>
  <revision>
    <id>1055</id>
    <parentid>956</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Notepad.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Screen01.gif</title>
  <ns>6</ns>
  <id>111</id>
  <revision>
    <id>1056</id>
    <parentid>514</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Screen01.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:98650015.zip</title>
  <ns>6</ns>
  <id>233</id>
  <revision>
    <id>1057</id>
    <parentid>846</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:98650015.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">98650015 ROM.</text>
    <sha1>eaadf0a6a6abadc50b6aa15fda1277488fb92654</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:OBD-connector-pinout.png</title>
  <ns>6</ns>
  <id>238</id>
  <revision>
    <id>1058</id>
    <parentid>860</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:OBD-connector-pinout.png]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">OBD-II connector pinout, from the factory service manual.</text>
    <sha1>a35c921450cf6679a365181365bedd20f6c7b126</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Screen04.gif</title>
  <ns>6</ns>
  <id>115</id>
  <revision>
    <id>1059</id>
    <parentid>518</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Screen04.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88590015-v5.10.zip</title>
  <ns>6</ns>
  <id>132</id>
  <revision>
    <id>1060</id>
    <parentid>559</parentid>
    <timestamp>2016-01-11T00:11:33Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88590015-v5.10.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="108" xml:space="preserve">88590015 Rom file, Rom definition, Rom base definition. Preloaded with Tephra v5.10 and mrfreds definitions.</text>
    <sha1>66f1bc48729b936f84c66bb13f97fef9d67894ea</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Port.jpg</title>
  <ns>6</ns>
  <id>92</id>
  <revision>
    <id>1061</id>
    <parentid>311</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Port.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Picture of OBD2 port</text>
    <sha1>e0298cfddbb50869adb764060f6d2cfcf4c130a4</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:94170715-v7.zip</title>
  <ns>6</ns>
  <id>253</id>
  <revision>
    <id>1062</id>
    <parentid>947</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170715-v7.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">XML and ROM for Tephra v7 of  94170015</text>
    <sha1>d9d32baa60a1db698e171cda418ac40db49c7714</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Cable.jpg</title>
  <ns>6</ns>
  <id>84</id>
  <revision>
    <id>1063</id>
    <parentid>303</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Cable.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">Picture of Tactrix Cable</text>
    <sha1>ef7bd57644bca4f29d83bda209e058828fb01e40</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:BoostErrorAdjusted.gif</title>
  <ns>6</ns>
  <id>126</id>
  <revision>
    <id>1064</id>
    <parentid>529</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:BoostErrorAdjusted.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Fuelmap.jpg</title>
  <ns>6</ns>
  <id>95</id>
  <revision>
    <id>1065</id>
    <parentid>314</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Fuelmap.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8" xml:space="preserve">fuel map</text>
    <sha1>73fdd73966eb292d176fcd2c8541ccf2f97e1dd6</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Screen03.gif</title>
  <ns>6</ns>
  <id>114</id>
  <revision>
    <id>1066</id>
    <parentid>517</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Screen03.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:90550001 EVO7-RA Stock.zip</title>
  <ns>6</ns>
  <id>154</id>
  <revision>
    <id>1067</id>
    <parentid>673</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:90550001 EVO7-RA Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Openfile.jpg</title>
  <ns>6</ns>
  <id>91</id>
  <revision>
    <id>1068</id>
    <parentid>310</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Openfile.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">how to load a map</text>
    <sha1>f5dad466bd61f04b6d405d32f42b7dcbc29bb414</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Beer.gif</title>
  <ns>6</ns>
  <id>109</id>
  <revision>
    <id>1069</id>
    <parentid>512</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Beer.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:94170008 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>173</id>
  <revision>
    <id>1070</id>
    <parentid>706</parentid>
    <timestamp>2016-01-11T00:11:34Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:94170008 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:96530006.HEX</title>
  <ns>6</ns>
  <id>61</id>
  <revision>
    <id>1071</id>
    <parentid>191</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96530006.HEX]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46" xml:space="preserve">2005 EDM Mitsubishi Lancer Evolution ROM image</text>
    <sha1>e4a308fc6aac945331c1616cf9f259366bee6d47</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Standalone AEM Serial.jpg</title>
  <ns>6</ns>
  <id>270</id>
  <revision>
    <id>1072</id>
    <parentid>974</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Standalone AEM Serial.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="125" xml:space="preserve">Image of how to construct an AEM UEGO cable serial connection to mini 1/8" connection for use in standalone logging on OP2.0.</text>
    <sha1>1736a34aa941eb2f0d26ce936c3c79a6e452439f</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:98640016 Evo7 Stock.zip</title>
  <ns>6</ns>
  <id>203</id>
  <revision>
    <id>1073</id>
    <parentid>772</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:98640016 Evo7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:LeanSpoolCompare.gif</title>
  <ns>6</ns>
  <id>128</id>
  <revision>
    <id>1074</id>
    <parentid>531</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:LeanSpoolCompare.gif]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Def file 96530006 tephra510 new tables 20081101.zip</title>
  <ns>6</ns>
  <id>151</id>
  <revision>
    <id>1075</id>
    <parentid>646</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Def file 96530006 tephra510 new tables 20081101.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="64" xml:space="preserve">included primer tables and in evo7base also perephery bits added</text>
    <sha1>6ca364c26bdad5d97f162063487010295dbcab03</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:20090528WGDC 100p under load.JPG</title>
  <ns>6</ns>
  <id>221</id>
  <revision>
    <id>1076</id>
    <parentid>824</parentid>
    <timestamp>2016-01-11T00:11:35Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:20090528WGDC 100p under load.JPG]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="59" xml:space="preserve">Shows "Tephramod WGDC 100% under this load" characteristic.</text>
    <sha1>d7d557c94bf4d8e9891457744e5c13d8c38adaff</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:97470001 EVO8 Stock.zip</title>
  <ns>6</ns>
  <id>166</id>
  <revision>
    <id>1077</id>
    <parentid>697</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:97470001 EVO8 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:93390000 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>146</id>
  <revision>
    <id>1078</id>
    <parentid>622</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:93390000 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Stock rom</text>
    <sha1>880dbd4e99605d928c097bf538048da4d0b3aac8</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:88840017 EVO9 Stock.zip</title>
  <ns>6</ns>
  <id>190</id>
  <revision>
    <id>1079</id>
    <parentid>750</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88840017 EVO9 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001130|1031">
  <title>File:Monamona-cablle-schematic.pdf</title>
  <ns>6</ns>
  <id>263</id>
  <revision>
    <id>1080</id>
    <parentid>963</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:Monamona-cablle-schematic.pdf]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:99860002 EVO7 Stock.zip</title>
  <ns>6</ns>
  <id>177</id>
  <revision>
    <id>1081</id>
    <parentid>710</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:99860002 EVO7 Stock.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:96530006+tephra510+new tables.zip</title>
  <ns>6</ns>
  <id>147</id>
  <revision>
    <id>1082</id>
    <parentid>625</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:96530006+tephra510+new tables.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:88780004.hex</title>
  <ns>6</ns>
  <id>217</id>
  <revision>
    <id>1083</id>
    <parentid>802</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:88780004.hex]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:1g aldl schematic complete.jpg</title>
  <ns>6</ns>
  <id>255</id>
  <revision>
    <id>1084</id>
    <parentid>950</parentid>
    <timestamp>2016-01-11T00:11:36Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:1g aldl schematic complete.jpg]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="66" xml:space="preserve">More complete cable schematic for a 1g DSM ALDL datalogging cable.</text>
    <sha1>b7b8d1618707e05a080475b8341a980c40be6616</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:90550001-v5.10fix-mods.zip</title>
  <ns>6</ns>
  <id>138</id>
  <revision>
    <id>1085</id>
    <parentid>599</parentid>
    <timestamp>2016-01-11T00:11:37Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:90550001-v5.10fix-mods.zip]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14" xml:space="preserve">90550001-v5.10</text>
    <sha1>9ab63b79a2be56522290ba9c3e3fa7eafe74a44b</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:1byteload spikes sm.JPG</title>
  <ns>6</ns>
  <id>219</id>
  <revision>
    <id>1086</id>
    <parentid>822</parentid>
    <timestamp>2016-01-11T00:11:37Z</timestamp>
    <contributor>
      <username>Maintenance script</username>
      <id>0</id>
    </contributor>
    <comment>Maintenance script uploaded [[File:1byteload spikes sm.JPG]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="29" xml:space="preserve">Shows 1 byte load wrap-around</text>
    <sha1>90c4492a9a77f48c5a446f55f9907529d55a132b</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1087</id>
    <parentid>1</parentid>
    <timestamp>2016-01-11T00:32:07Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/MediaWiki default|MediaWiki default]] ([[User talk:MediaWiki default|talk]]) to last revision by [[User:EdwardMarshall|EdwardMarshall]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2777" xml:space="preserve">'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.  

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

{{note|''Editors!'' if you're here to add a new page to the wiki, we appreciate the help! But please, check to see if it doesn't already exist first; we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. Just search for your topic in the sidebar, and see if there's something similar already; if there is, please help us improve by augmenting and cleaning up existing articles. Thanks!}}

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''.  If you are not careful you can destroy your ECU or worse, your engine.  If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health.  Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you.  Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM.  Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.</text>
    <sha1>983a7ec324fdc2de151e03d238cfb94e0fcdaf6c</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>File:Evoecu-logo.jpg</title>
  <ns>6</ns>
  <id>274</id>
  <revision>
    <id>1088</id>
    <timestamp>2016-01-11T07:10:18Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <comment>Evo Ecu Wiki logo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">Evo Ecu Wiki logo</text>
    <sha1>814661075bbfe0d3a3af46eb3562dcf9a7200dce</sha1>
  </revision>
</page>
<page arvcontinue="20160111001136|1081">
  <title>Downloads</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>1089</id>
    <parentid>364</parentid>
    <timestamp>2019-12-18T00:54:24Z</timestamp>
    <contributor>
      <username>EdwardMarshall</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2335" xml:space="preserve">Here you will find ROM's, ROM definitions, and EvoScan setting files.  In order to use the download section you will need to find the ROM ID below that matches your car year and type.  Once you have selected your rom type you will find several packages containing a ROM, ROM definition, and EvoScan setting file.  Select the package that matches the ECU patches you would like to use. 

IMPORTANT! 
These WILL NOT contain altered maps from a tuned ECU. If you plan to use these and are already tuned you will need to copy your maps to these roms! At a minimum you will always need to copy your immobilizer code. 

Please read the !Readme.txt included in zip files 

If you're not finding what you're looking for here, take a peek at: https://evoecu.logic.net/mirror/svn/roms/stock/

[[:Category:ROMs]]

{| border=1 cellpadding=3 cellspacing=0 
|'''Year'''
|'''Market'''
|'''Version'''
|'''Rom file'''
|'''Notes'''
|-
|2001
|JDM
|Evo 7 
|[[93390000]]
|
|-
|2001
|JDM
|Evo 7 RA
|[[92460000]]
|
|-
|2001
|JDM
|Evo 7 
|[[99860002]]
|
|-
|2001
|EDM
|Evo 7 RA
|[[90550001]]
|
|-
|2002
|USDM
|Mirage LS 1.8 
|[[90160003]]
|
|-
|2002
|AUDM
|Evo 7 GT-A
|[[80700010]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650012]]
|
|-
|2003
|EDM
|Evo 7 RA
|[[98650015]]
|
|-
|2004
|JDM
|Evo 8 
|[[96260009]]
|

|-
|2004
|USDM
|Evo 8
|[[94170008]]
|
|-
|2004
|USDM
|Evo 8
|[[94170014]]
|
|-
|2004
|USDM
|Evo 8
|[[94170015]]
| 
|-
|2004
|USDM
|Evo 8
|[[96420007]]
|
|-
|2004
|USDM
|Evo 8
|[[96420008]]
|
|-
|2004
|???
|Evo 8 GSR RA
|[[97250001]]
|
|-
|2004
|JDM
|Evo 8
|[[93660005]]
|
|-
|2004
|EDM
|Evo 8 
|[[99270000]]
|
|-
|2005
|EDM
|Evo  8
|[[96530006]]
|"Universal" VIII ROM.
|-
|2005
|USDM
|Evo 8 
|[[96940011]]
|
|-
|2005
|EDM
|Evo 9 GSR 
|[[88840013]]
|
|-
|2005
|AUSDM
|Evo 9
|[[88580013]]
|
|-
|2005
|
|Evo 9
|[[88580015]]
|
|-
|2005
|JDM
|Evo 9 GSR
|[[88570008]]
|
|-
|2005
|JDM
|Evo 9 GTA
|[[88780004]]
| 
|-
|2006
|JDM
|Evo 9
|[[89280002]]
|
|-
|2006
|USDM
|Evo 9
|[[88590013]]
|
|-
|2006
|USDM
|Evo 9
|[[88590014]]
|
|-
|2006
|USDM
|Evo 9
|[[88590015]]
|
|-
|2006
|USDM
|Evo 9 MR (Mexican market)
|[[88840016]]
|
|-
|2006
|AUDM
|Evo  9
|[[88580014]]
|
|-
|2006
|EDM
|Evo 9 
|[[88840017]]
|
|-
|2006
|JDM
|Evo 9 
|[[89960000]]
| 6 Speed
|-
|
|
|Evo 
|[[98650014]]
|
|-
|
|
|Evo 
|[[98640016]]
|
|-
|
|
|Evo 
|[[96420011]]
|
|-
|
|
|Evo 
|[[95960000]]
|
|}</text>
    <sha1>765d7e9e96dffbd1f1a1d9b6b3c4e437264a27b0</sha1>
  </revision>
</page>
</mediawiki>